Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase

Why do I need a dedicated SQL server? Expand / Collapse
Author
Message
Posted Monday, March 1, 2010 9:08 AM
Grasshopper

GrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopper

Group: General Forum Members
Last Login: Wednesday, February 13, 2013 1:08 PM
Points: 11, Visits: 45
I need to come up with the benefits of having a dedicated SQL Server and thought I would ask here to make sure I don't forget anything.

We currently have a 25GB database with up to 200 users.

Please respond with as many benefits why a company would use a dedicated server rather than sharing it with many other databases.


Thank You!
Post #874480
Posted Monday, March 1, 2010 9:18 AM


Ten Centuries

Ten CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen Centuries

Group: General Forum Members
Last Login: Yesterday @ 4:45 PM
Points: 1,296, Visits: 2,778
Dedicated server? Do you mean a single instance (default or named) hosting a single database? Here are some benefits of a separate instance:

Can allocate specific memory to that instance
Can control access thru its defined port and firewall rules
Because there's separate services, it can be serviced separate from other databases on the server (or vice versa)
Can have specific configuration settings for this instance, for security/performance/maintenance

There's just a few, probably plenty more to think about.


----------------------------------------------------------------------------
Sacramento SQL Server users group - http://sac.sqlpass.org
Follow me on Twitter - @SQLDCH
----------------------------------------------------------------------------

Yeah, well...The Dude abides.
Post #874485
Posted Monday, March 1, 2010 9:50 AM
SSC-Enthusiastic

SSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-EnthusiasticSSC-Enthusiastic

Group: General Forum Members
Last Login: Friday, August 15, 2014 2:02 PM
Points: 137, Visits: 493
Whether it requires a dedicated server for the database, you need to consider its application importance, security, availability, performance, and manageability. Here are some thoughts for having a dedicated database server:

Application Importance - If this database supports a critical application, why can't you afford a dedicated server for it to generate more revenue or benefits for the company?

Security - If you want to avoid unrelated people to potentially view the data, dedicated server is a choice.

Availability - The other database instance(s) on the same server may be unstable and requires frequent server reboot that reduces your database availability.

Performance - Your database instance may compete computer resources with other instances that may cause undesired performance to your database.

Manageability - It require more coordination for many things in a shared environment and this coordination is not always an easy task.



Post #874515
Posted Monday, March 1, 2010 10:11 AM


SSC-Insane

SSC-InsaneSSC-InsaneSSC-InsaneSSC-InsaneSSC-InsaneSSC-InsaneSSC-InsaneSSC-InsaneSSC-InsaneSSC-InsaneSSC-Insane

Group: General Forum Members
Last Login: Today @ 3:27 PM
Points: 21,631, Visits: 15,289
dbychen gave some good responses. In addition I would add easier troubleshooting (no other apps interfering).



Jason AKA CirqueDeSQLeil
I have given a name to my pain...
MCM SQL Server


SQL RNNR

Posting Performance Based Questions - Gail Shaw
Posting Data Etiquette - Jeff Moden
Hidden RBAR - Jeff Moden
VLFs and the Tran Log - Kimberly Tripp
Post #874528
Posted Tuesday, March 2, 2010 7:53 AM
Grasshopper

GrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopper

Group: General Forum Members
Last Login: Wednesday, February 13, 2013 1:08 PM
Points: 11, Visits: 45
Thanks for the responses... much appreciated!
Post #875182
Posted Tuesday, March 2, 2010 9:23 AM


SSC-Insane

SSC-InsaneSSC-InsaneSSC-InsaneSSC-InsaneSSC-InsaneSSC-InsaneSSC-InsaneSSC-InsaneSSC-InsaneSSC-InsaneSSC-Insane

Group: General Forum Members
Last Login: Today @ 3:27 PM
Points: 21,631, Visits: 15,289
scott.trick (3/2/2010)
Thanks for the responses... much appreciated!


You're welcome.




Jason AKA CirqueDeSQLeil
I have given a name to my pain...
MCM SQL Server


SQL RNNR

Posting Performance Based Questions - Gail Shaw
Posting Data Etiquette - Jeff Moden
Hidden RBAR - Jeff Moden
VLFs and the Tran Log - Kimberly Tripp
Post #875276
Posted Saturday, March 13, 2010 9:34 PM


SSCarpal Tunnel

SSCarpal TunnelSSCarpal TunnelSSCarpal TunnelSSCarpal TunnelSSCarpal TunnelSSCarpal TunnelSSCarpal TunnelSSCarpal TunnelSSCarpal Tunnel

Group: General Forum Members
Last Login: Tuesday, August 19, 2014 3:55 PM
Points: 4,186, Visits: 4,264
I tried making making this argument for many of the reasons
that were suggested in this thread and my advise was taken during a consolidation exercise.

I had one poorly designed unstable Database, etc. THis Database was a revenue generated.

The audience were Network Admin's so I tried to make and analogy.

You want to make sure that you Databases that you place a a Server Play nice in the Sandbox together.

It stated that if you put an unstable resource hog on a Server with other mission critical Databases then you put your Business at risk.



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/

Post #882478
Posted Saturday, March 13, 2010 9:35 PM


SSCarpal Tunnel

SSCarpal TunnelSSCarpal TunnelSSCarpal TunnelSSCarpal TunnelSSCarpal TunnelSSCarpal TunnelSSCarpal TunnelSSCarpal TunnelSSCarpal Tunnel

Group: General Forum Members
Last Login: Tuesday, August 19, 2014 3:55 PM
Points: 4,186, Visits: 4,264
I tried making making this argument for many of the reasons
that were suggested in this thread and my advise was taken during a consolidation exercise.

I had one poorly designed unstable Database, etc. THis Database was a revenue generated.

The audience were Network Admin's so I tried to make and analogy.

You want to make sure that the Databases that you place a a Server Play nice in the Sandbox together.

It respectfully stated that if you put an unstable resource hog on a Server with other mission critical Databases then you put your Business at risk.



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/

Post #882479
Posted Tuesday, August 10, 2010 5:11 PM
Valued Member

Valued MemberValued MemberValued MemberValued MemberValued MemberValued MemberValued MemberValued Member

Group: General Forum Members
Last Login: Tuesday, August 5, 2014 6:13 PM
Points: 55, Visits: 276
Depending on your I/O needs too, SQL Server can be a bit of a resource hog. If you have SQL Server 2008, you can use Resource Governor though to help out with any issues on that end. A 25 GB database isn't that big, but you also need to consider its growth rate too. It depends on your hardware set up also as I don't know how big your drives are or how fast the boxes are.

Good points about security too as SysAdmins, Network Admins, etc. are going to need access to the box. If it's sensitive information (e.g. HR database), then that should be on its own box regardless as the less people with access to the box in any way, shape, or form, the better.
Post #967067
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse