Please start any new threads on our new
site at https://forums.sqlteam.com. We've got lots of great SQL Server
experts to answer whatever question you can come up with.
| Author |
Topic |
|
cedtech31
Starting Member
17 Posts |
 Posted - 2008-03-10 : 13:19:34
|
| I currently have ms sql 2000 sp4 installed, with the data files and log files both on a RAID 5. I want to separate the log file (.ldf) onto a RAID 1 to improve performance. I search for articles on the steps involved with no luck. Can someone point me to an article are tell me how to accomplish this task?Thanks |
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
Posted - 2008-03-10 : 13:29:53
|
| Just detach the database, move the file(s) to where you want, and then re-attach. You can do this through Enterprise Manager in the GUI or via sp_detach_db/sp_attach_db in Query Analyzer.Tara KizerMicrosoft MVP for Windows Server System - SQL Serverhttp://weblogs.sqlteam.com/tarad/ |
 |
|
|
ahcorrea
Starting Member
2 Posts |
Posted - 2008-03-25 : 14:38:58
|
| I too have seen these recommendations and wondered if all the ldf files can exist in the same physical location together. And all the mdf file can exist in the same physical location. |
|
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
Posted - 2008-03-25 : 14:45:35
|
| Yes.Tara KizerMicrosoft MVP for Windows Server System - SQL Serverhttp://weblogs.sqlteam.com/tarad/ |
|
|
|
ahcorrea
Starting Member
2 Posts |
Posted - 2008-03-25 : 15:14:34
|
| Thanks that's helpful.Allow me to take this a step further.....I have a customer that has a nightly System DB-maintenance plan that first checks the integrity of the the system db's, then optimizes them, followed by backing them up, and concluding with shrinking the db's. My problem lies in the tempdb transaction log.This maintenance plan shrinks the transaction log file at 2AM every night - usually ends up around 3 MB. Production processing of importing files and processing data in the customer db begins around 5AM and by 9 or 10 AM, the tempdb transaction log has grown to 3+ GB at 10% increments. Now, I know that I can change the growth increment to a set number rather than use a percentage, but if I already know that the end size is going to be between 2.5 and 4.5 GB, how can I have the 2AM process reduce shrink the file to a more manageable starting point - say 2 GB. |
|
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
Posted - 2008-03-25 : 15:17:44
|
| Remove the shrink job. You should not have this on a production system as you are just causing performance problems. Shrinks should only happen manually and only if the space is no longer needed in the near future.Tara KizerMicrosoft MVP for Windows Server System - SQL Serverhttp://weblogs.sqlteam.com/tarad/ |
|
|
|
|
|
|
separate .ldf and .mdf files