How do you decide which databases belong on which servers?

Question

How do you decide which databases belong on which servers?

Viewing 6 posts - 16 through 20 (of 20 total)

You must be logged in to reply to this topic. Login to reply

Jeffrey Williams SSC Guru Points: 90303 More actions · Answer 1

I would add SLA's to the list of items to consider.

If you have systems that are generally only needed/used during business hours, you really don't want to comingle them with your 24/7 critical systems. And that also leads to the maintenance windows and when you can access those systems for patching or upgrading.

Jeffrey Williams
“We are all faced with a series of great opportunities brilliantly disguised as impossible situations.”

― Charles R. Swindoll

How to post questions to get better answers faster
Managing Transaction Logs

Welsh Corgi SSC Guru Points: 116520 More actions · Answer 2

Jeffrey,

Excuse me Sir but Im not sure that I understand your post?

Regards,

WelshS

For better, quicker answers on T-SQL questions, click on the following...
http://www.sqlservercentral.com/articles/Best+Practices/61537/

For better answers on performance questions, click on the following...
http://www.sqlservercentral.com/articles/SQLServerCentral/66909/

Jeffrey Williams SSC Guru Points: 90303 More actions · Answer 3

Welsh Corgi (2/11/2010)
Jeffrey,
Excuse me Sir but Im not sure that I understand your post?
Regards,
WelshS

If you have a system that is only accessed during business hours, say from 7am to 7pm - and no users access that system after that time, then you don't want to put that database on a system where the users are going to be accessing their database 24/7.

When you have a critical system that must be up and running 24/7 - you really don't want a process from a non critical system taking up resources for that system and potentially causing performance issues.

So, it's not just about maintenance - it's about the service level agreements for each application/system. Some require a higher level of availability - and requirements, others require less and should be located on systems that are more appropiate to the level of service required.

Jeffrey Williams
“We are all faced with a series of great opportunities brilliantly disguised as impossible situations.”

― Charles R. Swindoll

How to post questions to get better answers faster
Managing Transaction Logs

Welsh Corgi SSC Guru Points: 116520 More actions · Answer 4

xxx

For better, quicker answers on T-SQL questions, click on the following...
http://www.sqlservercentral.com/articles/Best+Practices/61537/

For better answers on performance questions, click on the following...
http://www.sqlservercentral.com/articles/SQLServerCentral/66909/

Welsh Corgi SSC Guru Points: 116520 More actions · Answer 5

Thank you for the clarification...:-)

For better, quicker answers on T-SQL questions, click on the following...
http://www.sqlservercentral.com/articles/Best+Practices/61537/

For better answers on performance questions, click on the following...
http://www.sqlservercentral.com/articles/SQLServerCentral/66909/

Henry_Lee SSCrazy Points: 2714 More actions · Answer 6

Thanks all for the good feedback!

Steve, just to clarify, I didn't mean to imply we had Dev and Prod code on the same server. We of course have a separate box for testing. I was speaking more to the previous poster's remark about whether developers can touch production machines. Here, developers can put things in production - presumably after they've been tested. By the way I do intend on checking that white paper - thanks.