Solved

SQL install paths for 2008 R2

Posted on 2014-01-06
5
348 Views
Last Modified: 2014-01-06
When installing SQL I have seperated the data directories as atatched.  

Basically i'm using:  S for data and L for Logs.  

Is it ok to gorup user database lops and temp DB logs into the same L partion?

Any other comments/observatins on the directories I've used.  This is my first SQL install.
SQL-install.docx
0
Comment
Question by:DHPBilcare
  • 2
  • 2
5 Comments
 
LVL 25

Accepted Solution

by:
Lee Savidge earned 500 total points
Comment Utility
There is no reason why you shouldn't put the logs in the same partition. Basic installs will often see the database and logs in the same folder in the same partition. Larger scale system will separate these out onto different drives for performance.

If you've got a very high load on the system, then you could consider separating out the logs and data files onto separate drives but you need to balance performance out with cost and available hardware.
0
 

Author Comment

by:DHPBilcare
Comment Utility
It's a system which could grow but at the start the load wont be that high.

I'm just deciding if there is any reason why I would not want to group user logs and temp DB logs into the same partition and likewise for the user database and TempDB.
0
 
LVL 25

Expert Comment

by:Lee Savidge
Comment Utility
I personally can't think of a reason why you shouldn't.

With regards to growth and loadl this is a complex assessment to decide immediately. However, these things can be changed later so don't worry as nothing is st in stone and you probably won't get it dead on straight away anyway.
0
 

Author Comment

by:DHPBilcare
Comment Utility
Thanks!
0
 
LVL 59

Expert Comment

by:Kevin Cross
Comment Utility
I agree.  If it helps, a deciding factor for separating logs/data and, similarly, system databases from user ones is separate drive spindles and controllers.  If you have one set of physical drives partitioned into multiple volumes (logical drives), there really is not a difference in splitting up the data because you have not increased I/O capabilities in any way.  With multiple controllers, splitting up data files allows you to segment I/O of log away from data, system away from user, et cetera.

As stated, you likely will not guess right upfront, but do try to establish an initial size for tempDB and your databases that makes sense in a longer term.  In addition, take care with setting the file growth to something that will make sense as your data and usage grows.  In other words, growing a database in 1MB increments rarely makes sense in production.
0

Featured Post

Highfive Gives IT Their Time Back

Highfive is so simple that setting up every meeting room takes just minutes and every employee will be able to start or join a call from any room with ease. Never be called into a meeting just to get it started again. This is how video conferencing should work!

Join & Write a Comment

This article explains how to reset the password of the sa account on a Microsoft SQL Server.  The steps in this article work in SQL 2005, 2008, 2008 R2, 2012, 2014 and 2016.
How to update Firmware and Bios in Dell Equalogic PS6000 Arrays and Hard Disks firmware update.
This tutorial will walk an individual through the process of configuring basic necessities in order to use the 2010 version of Data Protection Manager. These include storage, agents, and protection jobs. Launch Data Protection Manager from the deskt…
This tutorial will show how to configure a new Backup Exec 2012 server and move an existing database to that server with the use of the BEUtility. Install Backup Exec 2012 on the new server and apply all of the latest hotfixes and service packs. The…

772 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

Need Help in Real-Time?

Connect with top rated Experts

10 Experts available now in Live!

Get 1:1 Help Now