September 10, 2009 at 4:27 pm
Hi George,
You are right. I should have installed databases on to the dedicated data drive and then move the logs to the Log folder.
I thought even though we install the database files onto a dedicated data drive, I should repeat the same process of moving the system database's log files onto a log drive I.e stopping the service, starting the master database in single user mode etc.
Thanks a lot for your help and guidance. You are always there to help guys like us who are in real trouble.
Thank You,
Yours,
SQLBuddy
September 10, 2009 at 4:41 pm
Its not worth moving the system database log files to another drive, theres no performance benefit and you just complicate your install process and put future upgrades at risk. Where databases are read only or rarely updated, such as system databases, there is no point seperating out the log files.
master database - rarely updated, leave mdf and ldf together
resource database - readonly, leave mdf and ldf together and with master database
distmdl files, leave together and with master
model database - very rarely updated, leave mdf and ldf together
msdb - updated, how much depending on no. of jobs. ssis packages, backups\restores, so some argument for moving ldf, but really unless you have a lot of log activity its just not worth it.
tempdb - this is the exception, if your environment uses tempdb heavily, move both files to a drive dedicated to tempdb. But again don't move it just for the hell of it.
---------------------------------------------------------------------
September 11, 2009 at 9:49 am
Hi George,
What a beautiful message! Tremendous indeed!
I will definitely keep this in mind and try to implement this strategy with my future SQL installs.
Once again, Thank you very much for all the unparalleled guidance and help you have provided to me.
Yours
SQLBuddy.
Viewing 3 posts - 16 through 17 (of 17 total)
You must be logged in to reply to this topic. Login to reply