January 16, 2004 at 11:30 am
Our SQL2000 cluster contains a default instance and 2 named instances. For most databases, there's a production, development, and test version. My question is:
Is it good practice to run your development and test databases on the same instance as your production one? and why?
Thanks,
Jen
January 16, 2004 at 12:52 pm
Personally, I don't like the thought of all DB environments on the same server. The potential of un-wanted access or modification to the production DB is to great. I do not have a great problem with the test DB as much as the development DB. Development is an environment where you not only create objects but may tune the server and DB for best performance. Changing server settings on a production machine is not the best practice for running a smooth enterprise.
January 16, 2004 at 1:58 pm
Thanks Newbie for your recommendations.
Jen
January 16, 2004 at 2:07 pm
My biggest issue is that the resources will be in contention. In dev it's easy for someone to test a new query and eat up all the CPU or an inordinate amoutn of RAM. You can fix RAM size by instance, but not CPU.
I don't worry about the security since it can be set to separate people per instance.
January 17, 2004 at 2:55 pm
Thanks Steve. Both your answers have convinced me to move the dev database off to another instance.
Jen
Viewing 5 posts - 1 through 4 (of 4 total)
You must be logged in to reply to this topic. Login to reply