[Webinar] Streamline your web hosting managementRegister Today

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 600
  • Last Modified:

SQL Server 2012 Installation Data Directories

I have 3 drives for my SQL Server 2012 installation. C = 50GB - D = 200GB - E - 50GB
When Im doing my SQL Server 2012 install I am at the Database Engine Configuration point and I want to know where I should be installing the following

Data Root Directory - C:Program Files\Microsoft SQL Server\ (default)
System database directory - set to default on C
User database directory - E:\Microsoft SQL Server\Data
User database log directory - F:\Microsoft SQL Server\Log
TempDB directory - E:\Microsoft SQL Server\Data
TempDB directory - F:\Microsoft SQL Server\Log
Backup Directory - set to default on C

I also have Business Intelligence databases that I have to configure as well with the same setup(Data, Log, Temp and backup)

I can add more disk space and I can also add drives if need be but I only have 1 SQL database that I will have my Datawarehouse tables on and I will have about 50 SSIS packages, maybe 10 cubes and I will be running Reporting Services as well. I know that I shouldnt have all these on one server but we have licensing issues with our source sytem that we will be pulling from so this new server will be using that license and we cant get another one because of the cost. So Im kinda stuck where thats concerned but as far as disk space and drives Im open to suggestions but I would like to keep as simple as I can...

Thanks I appreciate anyones help
0
jknj72
Asked:
jknj72
  • 3
  • 3
1 Solution
 
Aneesh RetnakaranDatabase AdministratorCommented:
I am not sure about your database size, but the data drive E seems to be small
If possible I will move the tempdb to another drive or to C:\ drive , and probably will add more data files for it. Better if you put them on different drives. You can see the recommended no of files on link below
http://www.sqlskills.com/blogs/paul/a-sql-server-dba-myth-a-day-1230-tempdb-should-always-have-one-data-file-per-processor-core/
0
 
jknj72Author Commented:
Im sorry E drive is 100GB. Is that still too small?
0
 
Aneesh RetnakaranDatabase AdministratorCommented:
that depends on your database size and Growth rate. 100 GB seems reasonable for a medium sized db
0
Problems using Powershell and Active Directory?

Managing Active Directory does not always have to be complicated.  If you are spending more time trying instead of doing, then it's time to look at something else. For nearly 20 years, AD admins around the world have used one tool for day-to-day AD management: Hyena. Discover why

 
jknj72Author Commented:
Ok then is my setup sufficient? Do I have everything on the right drives from what you can see?
0
 
Aneesh RetnakaranDatabase AdministratorCommented:
I think so, if you can, add one more data drive and add another tempdb data file there
0
 
Vitor MontalvãoMSSQL Senior EngineerCommented:
Backup Directory - set to default on C
So, do you think C: drive has enough space to handle all backups? If you have 200GB for D: how can a drive with 50GB will handle the operating system + MSSQL binaries + other programs + backups? You should have a separate drive only for backups.
If drive E: it's only for transaction log files I think the size is ok.
TempDB should also have a dedicated drive. You can put the tempdb_log in the same drive as tempdb_data files.
0
 
jknj72Author Commented:
I think this is what I am looking for. Im running into other problems so if you can help out id appreciate it
0

Featured Post

Creating Active Directory Users from a Text File

If your organization has a need to mass-create AD user accounts, watch this video to see how its done without the need for scripting or other unnecessary complexities.

  • 3
  • 3
Tackle projects and never again get stuck behind a technical roadblock.
Join Now