Why do I need a dedicated SQL server?

SQLServerCentral is supported by Red Gate Software Ltd.

Popular Topics

Home

Members

Calendar

Who's On

Home » Database Design » Hardware » Why do I need a dedicated SQL server?

Why do I need a dedicated SQL server?

Rate Topic

Display Mode

Topic Options

Author

Message

Scott T.

Posted Monday, March 01, 2010 9:08 AM

Grasshopper

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

SQLDCH

Posted Monday, March 01, 2010 9:18 AM

SSC Eights!

Group: General Forum Members
Last Login: Tuesday, May 07, 2013 7:41 PM
Points: 891, Visits: 2,263

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.

----------------------------------------------------------------------------
My LinkedIn profile - LinkedIn
Sacramento SQL Server users group - http://sac.sqlpass.org
My blog - http://www.expressnetsolutions.com/sqldch
Follow me on Twitter - @SQLDCH
----------------------------------------------------------------------------

Yeah, well...The Dude abides.

Post #874485

dbychen

Posted Monday, March 01, 2010 9:50 AM

SSC-Enthusiastic

Group: General Forum Members
Last Login: Wednesday, February 13, 2013 2:32 PM
Points: 135, Visits: 459

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? Tongue

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

SQLRNNR

Posted Monday, March 01, 2010 10:11 AM

SSCoach

Group: General Forum Members
Last Login: 2 days ago @ 1:46 PM
Points: 18,732, Visits: 12,329

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 2008

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

Scott T.

Posted Tuesday, March 02, 2010 7:53 AM

Grasshopper

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

SQLRNNR

Posted Tuesday, March 02, 2010 9:23 AM

SSCoach

Group: General Forum Members
Last Login: 2 days ago @ 1:46 PM
Points: 18,732, Visits: 12,329

scott.trick (3/2/2010)

Thanks for the responses... much appreciated!

You're welcome.

Post #875276

Welsh Corgi

Posted Saturday, March 13, 2010 9:34 PM

Hall of Fame

Group: General Forum Members
Last Login: 2 days ago @ 10:46 AM
Points: 3,820, Visits: 4,044

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

Welsh Corgi

Posted Saturday, March 13, 2010 9:35 PM

Hall of Fame

Group: General Forum Members
Last Login: 2 days ago @ 10:46 AM
Points: 3,820, Visits: 4,044

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

blackbird

Posted Tuesday, August 10, 2010 5:11 PM

Valued Member

Group: General Forum Members
Last Login: 2 days ago @ 10:34 AM
Points: 54, Visits: 237

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 »

Permissions