September 30, 2009 at 8:36 am
Our system drives are often created with very little spare space by the people who build the servers. We usually have no choice but to move the system database files. I have a script that moves them one database at a time. I wrote it based on the procedures in Books Online for moving system databases and I've never had any problems with it. Just make sure that the NTFS permissions are correct on the location you move the files to.
John
September 30, 2009 at 9:01 am
You will find that applying maintenance for SQL Server 2005 and 2008 will use a LOT of space on the sytem drive. Most of this goes into the Global Assembly Cache (GAC) that can only exist on the system drive.
The system databases are the least of your worries.
For SQL 2005 and assuming you install all components (AS, RS, IS, etc), if you start with the RTM build and allow space for 3 Service Packs and 10 CU updates, this will take about 8.2 GB on the system drive. You will also need about 0.5 GB extra free space for workfiles during a SP or CU install.
For SQL 2008, the same scenario is likely to use 15 GB of system drive space, and you will need about 2GB extra free space during a SP install.
Original author: https://github.com/SQL-FineBuild/Common/wiki/ 1-click install and best practice configuration of SQL Server 2019, 2017 2016, 2014, 2012, 2008 R2, 2008 and 2005.
When I give food to the poor they call me a saint. When I ask why they are poor they call me a communist - Archbishop Hélder Câmara
September 30, 2009 at 10:13 am
Our system drives are often created with very little spare space by the people who build the servers. We usually have no choice but to move the system database files. I have a script that moves them one database at a time. I wrote it based on the procedures in Books Online for moving system databases and I've never had any problems with it. Just make sure that the NTFS permissions are correct on the location you move the files to
Hi John,
You move System database files BUT do you keep .mdf & .ldf files of System databases together on same drive? OR
.mdf files of System databases on one drive (like D:\SQLDATA) and .ldf files on another drive (like E:\SQLLOgs)??
thanks
September 30, 2009 at 10:17 am
I usually move them to different drives. There isn't any great dogma behind this - it's just that since I have data files on one drive and log files on another, I apply the same rule to system databases. It works, but equally it would work if I put them all on the same drive.
John
September 30, 2009 at 12:07 pm
from BOL..
"The Resource data and log files must reside together and must be in the same location as the master data file (master.mdf) "
So I just want to make sure that you are following the above rule or not?
In my case, I'm following that...Keeping Resource data and log files together master.mdf..
thanks
October 1, 2009 at 1:40 am
I can't find where it says that in SQL Server 2005 Books Online. I have the April 2006 edition. The closest I can find is the following:
If you move the master database, you must also move the Resource database to the same location as the master data file.
You could (and maybe should) interpret that as meaning that the Resource data and log files should go in the same location as the master data file. However, I have master and Resource data files in one location and master and Resource log files in another on several servers and nothing has broken yet. Having read this more carefully now, I may reconsider this policy for future installations.
John
October 1, 2009 at 4:42 pm
I can't find where it says that in SQL Server 2005 Books Online. I have the April 2006 edition. The closest I can find is the following:
If you move the master database, you must also move the Resource database to the same location as the master data file
.
Please go through this link..you will find it...
http://msdn.microsoft.com/en-us/library/ms345408%28SQL.90%29.aspx
Thanks
Viewing 7 posts - 16 through 21 (of 21 total)
You must be logged in to reply to this topic. Login to reply