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 |
|
nicolo
Starting Member
20 Posts |
 Posted - 2008-09-15 : 11:48:19
|
| My company uses electronic content management software to store hundreds and hundreds of scanned images to a server. The software utilizes MS SQL 2000 to create the databases and store the document structure. Unfortunately when this was installed the person put the entire thing on the C drive, software, data and log files in all. The name of the database created by the software is ScannedDocuments and that sits on the second drive. The C drive is running out of space while tempdb grows to over 1GB. On the second drive, drive D, ScannedDocuments has grown to over 4GB with a 1GB log file. I don't have many options to migrate these files around because I have no other drives. What can I do to shrink or manage them?I want to more importantly shink tempdb without any negative effect on ScannedDocuments. |
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
Posted - 2008-09-15 : 12:32:42
|
| 1GB is quite small for tempdb. For performance reasons, we configure it to be 8GB. You can shrink databases via the DBCC SHRINKFILE or DBCC SHRINKDATABASE commands, however I would highly not recommend this as there is a reason why the database grew to that size in the first place. You are only going to create performance issues by shrinking them. Get your company to add more disk space, preferably by creating an E (or another driver letter) drive.Tara KizerMicrosoft MVP for Windows Server System - SQL Serverhttp://weblogs.sqlteam.com/tarad/Subscribe to my blog |
 |
|
|
nicolo
Starting Member
20 Posts |
Posted - 2008-09-15 : 13:54:14
|
| yes 1GB is small for tempdb but in relation to the small C partition size, it's kind of big. Upon check it out, there is a weekly script that runs and maintains the ScannedDocuments database. But like you said, if it grew to that size it's because there are alot of transactions and there are things constantly being added and deleted on a daily basis. I don't have any other room for a drive, it's pretty much maxed out. |
|
|
|
james_wells
Yak Posting Veteran
55 Posts |
Posted - 2008-09-15 : 18:57:45
|
| If 1GB is relative large in relation to your C disk then i suspect that you have a small disk C: ?I would not shrink the TEMPDB while your disk configuration remains the same. If you can purchase more disk space then by moving the tempdb and the transaction logs to their own disk will have a huge improvement in performance. As the transactuion log is basically a sequential file the read/write heads are mostly always in the correct position to write/expand the transaction log. The TEMPDB is recreated every time the SQL Instance is restarted and therefore if a restart is possible depending on your operational requirements changes to the TEMPDB and the moving of the TERMPDB can be acheived. |
|
|
|
nicolo
Starting Member
20 Posts |
Posted - 2008-09-16 : 10:02:56
|
| what about moving tempdb and it's transaction logs to a NAS device? Is that too slow? I honestly have no more room to fit another drive in the server itself. |
|
|
|
james_wells
Yak Posting Veteran
55 Posts |
Posted - 2008-09-16 : 15:46:43
|
| If this is a dedicated server and no significant free space can be found or non related data moved to another server or new disks cannot be added then i would suggest that your only options is to build a new sql server, reinstall sql etc and then migrate the databases to the new server.Not sure what funds are available to you but spending money on new hardware is sometimes the only optionas as the alternative options are only delaying what really needs to be done.Sorry I can not be more positive. |
|
|
|
|
|
|
|
|
help with tempdb and my own DB