databases on system c drive

What if any risks are there in housing user and system drives on the c drive of a windows server. And do ms themselves recommend against it in any of their references?
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

Paul MacDonaldDirector, Information SystemsCommented:
Microsoft advocates separating database and log files.  It stands to reason neither should be on a system drive, if performance is a priority.

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
Paul MacDonaldDirector, Information SystemsCommented:
Mohammed KhawajaManager - Infrastructure:  Information TechnologyCommented:
Below are some of the risks:

1.  OS running out of disk space due to log or database files growing large
2.  Performance as disk will be taxed by OS, logs and read and write to the DB
3.  Potential data loss:  You separate logs and databases to ensure you do not lose both database and log files due to a disk failure
Ultimate Tool Kit for Technology Solution Provider

Broken down into practical pointers and step-by-step instructions, the IT Service Excellence Tool Kit delivers expert advice for technology solution providers. Get your free copy now.

Lee W, MVPTechnology and Business Process AdvisorCommented:
A single logical drive, in addition to the issues above, also reduces your flexibility in management and migration.  I use multiple logical drives as a form of hard quota so no one service eats up disk space and kills all services and so that, for example, if I replace the server, I can just move the VHD/VHDX to a new server - one large file copy is MUCH faster than copying thousands or millions of little files to a new server.  Further, I can create test networks much more quickly by only copying C: drives and selected data drives instead of ENTIRE systems.  (And these days, I ONLY install in VMs UNLESS there's a highly specific reason not to!)
pma111Author Commented:
Do all the above apply to both system and user databases or can you get away with storing system databases on the system drive
Lee W, MVPTechnology and Business Process AdvisorCommented:
Why would you want to?
Anthony PerkinsCommented:
Why would you want to?
I suspect the author's install has the system databases already on the C: drive and they are unsure/fearful of moving them.
Gerald ConnollyCommented:
@pma111 - you want your databases of whatever flavour to have consistent performance, if its on the C: drive its having to compete with all the system stuff for disk IOPS and MB/s

So no its not a good idea to have any DB's on your system disk.
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft SQL Server

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.