Want to protect your cyber security and still get fast solutions? Ask a secure question today.Go Premium

x
?
Solved

user and system DB on system drive

Posted on 2014-10-28
2
Medium Priority
?
119 Views
Last Modified: 2014-11-12
Do any of you store your system and user databases on your servers system drive, or do you store them on non system drives? Are there any risks in keeping them on the system drive, or any benefits in moving them to non system drives?
0
Comment
Question by:pma111
2 Comments
 
LVL 23

Accepted Solution

by:
Steve Wales earned 1000 total points
ID: 40408609
By default, Microsoft puts the system databases on the C: drive.

The major risk is that if something happens where one of the databases starts growing uncontrollably (which shouldn't happen with a system database but you never now) and the OS drive fills, then Windows grinds to a halt.

If tempdb is on your OS drive and your app or developers create huge temp tables frequently, that could cause it too.

Microsoft provides this note for moving system databases: http://msdn.microsoft.com/en-us/library/ms345408.aspx
0
 
LVL 31

Assisted Solution

by:Rich Weissler
Rich Weissler earned 1000 total points
ID: 40408611
On small servers, especially single purpose / express edition servers... I sometimes only have a single volume/drive to work with.

On slightly larger servers, the hardware guys will split out a system drive from the data drive, but it uses the same physical RAID set.  At that point, I believe I have a disadvantage of separating anything, and I put all the databases on the data drive.  (If the data drive fills up, that's bad, but it doesn't prevent the system from patching or cause operating system problems.)

On larger systems, I usually have a system volume, which will only have the database executables.  On different volumes I have the (1) database files, (2) transaction log files, and (3) [slowest disks] backup files.  But all that only applies when the different disks aren't on common physical disks... usually when I have volumes on the SAN.  If I had even large systems still, I'd split off the tempdb to it's own volume as well.

In my environment, the benefit to splitting the databases to a non-system volume is (hopefully) decreased I/O contention.  (Page file, OS Logs, and patching operations are written to the system volume.  All the database stuff should only have to contend with I/O traffic on it's own set of disks.)
0

Featured Post

Get your Disaster Recovery as a Service basics

Disaster Recovery as a Service is one go-to solution that revolutionizes DR planning. Implementing DRaaS could be an efficient process, easily accessible to non-DR experts. Learn about monitoring, testing, executing failovers and failbacks to ensure a "healthy" DR environment.

Question has a verified solution.

If you are experiencing a similar issue, please ask a related question

In the first part of this tutorial we will cover the prerequisites for installing SQL Server vNext on Linux.
This shares a stored procedure to retrieve permissions for a given user on the current database or across all databases on a server.
Using examples as well as descriptions, and references to Books Online, show the documentation available for date manipulation functions and by using a select few of these functions, show how date based data can be manipulated with these functions.
Via a live example combined with referencing Books Online, show some of the information that can be extracted from the Catalog Views in SQL Server.
Suggested Courses

578 members asked questions and received personalized solutions in the past 7 days.

Join the community of 500,000 technology professionals and ask your questions.

Join & Ask a Question