asked
How to test SQL 2000?
Hi everybody... I need to know, if my server would work properly if i downgrade from SQL 2000 Ent to SQL 2000 Stan. This is because we want to know if is necessary to have an Ent licence or not. The principal difference for us, that I found, is the memory... so I configured the max SQL Memory to 2048MB in SQL Ent, and the Monitor still running... is this Ok? or I forgot something? I don't see that the sql Service get slow ... mmm... I'm doing something bad? We have OLAP Servers also, but in virtualized servers... both are in Ent. but I think we can downgrade this one too... so what do you recommend? I'll be waiting for your recommendations. Thanks! Regards,
I would suggest building a new server with SQL 2000 standard on it and restoring your database to it so that you can test your system fully without risking your live setup. If you have the Enterprise license though why are you thinking of moving away from it?
I don't have the machine, and I don't have the time neather... The point is that next year probably we won't need the SQL because SAP is being implemented... so we don't wan't to invert to much money only for a year, and we need to know the results asap to know if we pay or not, because aduditing actions.
I am confused, what money are you investing in SQL Server for the coming year? Surely the license was purchased years ago? Is this a hosted service?
To test this out, I'd migrate the databases to a test machine with 2000 Standard edition. Then, capture a few hours of queries using a server side trace and then replay those queries in the Standard edition. Standard testing. It's the only way to be sure. You have to look at CPUs, you have less with standard. Ram can only be 2gb on standard. There are other differences, including some advanced OLAP stuff. [Check this link][1]. [1]:
http://www.microsoft.com/sql/prodinfo/previousversions/default.mspx
I have downgraded numerous SQL servers. Each time was a pretty good risk. To downgrade means uninstall and reinstall. If you are already licensed for Enterprise then I wouldn't risk it. You mentioned you also have a virtual environment, have you considered have a P2V done on the SQL server and do your testing with it. There will be some work there with renaming the box, updating the SQL instance name etc but at least you will be able to do your testing outside of production. As @grant fritchey and @fatherjack have mentioned there are ways to test if you are using Enterprise Ed features. I feel for you with this project you have been given. No test environment and no time to do the proper research and testing but yet they want a flawless execution.
I would not perform a downgrade from one unsupported editition to another unsupported edition. If you are demnaded to do a downgrade, you should demand that you should downgrade to a supported edition (like SQL 2008R2) and you get proper time and resources for lots of testing. If you do a downgrade to SQL 2000 standard, you still face the future upgrade to a supported edition.
