I want to recommend that our development shop setup a QA box that closely simulates production. My manager said to put together a proposal. Right now the development box is too small and has an older version of SQL Server, plus the operating system is NT. I'm wondering how to setup the environment. Getting the machine is the simple part. Should we get MSDN Universal, install the same operating system as production (Windows 2000 server) and the same database (SQL Server 2000)? That seems like the least expensive way. What has been your experience?
You're right on target with the suggestion that your QA environment closely model the production environment as much as possible. Different versions of SQL are just ASKING for compatibility problems down the road, and mismatched operating systems will have you spending more time troubleshooting than it would cost to upgrade to current versions. (You can easily prove that ROI to your manager -- wasted employee time is far more painful to a company's bottom line than coughing up the money for license fees.) MSDN is an excellent way to save money on licensing for testing and development environments. I would also make sure that your QA server has similar amounts of RAM dedicated to the SQL Server process, for the best results.
Do you have comments on this Ask the Expert Q&A? Let us know.
Dig Deeper on SQL Server Database Modeling and Design
Find how to create a SQL Server 2000 login account and then set user account rights to specific databases with "db_owner."
Learn why SQL Server 2000 connection is lost on the client side when database administrator changes 'SA' password on the SQL Server domain.
Learn how to create a SQL Server user authentication schema having password and tracked data changes requirements and how it involves Windows ...
Have a question for an expert?
Please add a title for your question
Get answers from a TechTarget expert on whatever's puzzling you.