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 |
|
jpotucek
Constraint Violating Yak Guru
273 Posts |
 Posted - 2006-06-12 : 15:43:58
|
| Forgive my ignornace, but I've already been to BOL and I still don't really understand what to do. We have an Application that has gotten extremely sluggish as of late. Then SOftware Vendor has suggested that we Truncate the log to improve performance. This is what I have: From EM, it shows the Database as being 122mb in size with 0.00 space available. both the log and data files are set to grow automatically by 10%The Database is in SIMPLE Recovery Mode. I have plently of Harddrive space on both the drive where the Data file lives and on the Drive where the logfile lives. Any suggestions on Truncating the log????? |
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
Posted - 2006-06-12 : 15:52:39
|
| Truncating the log will not improve performance. Also, you can not truncate a log when using SIMPLE recovery model. If the database is 122MB, then all queries should be relatively fast unless the queries and/or the database are poorly designed.Tara Kizeraka tduggan |
 |
|
|
jpotucek
Constraint Violating Yak Guru
273 Posts |
Posted - 2006-06-12 : 15:57:02
|
| Thanks Tara. Do you think that the DB have 0.00 space available is a problem? |
|
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
Posted - 2006-06-12 : 16:00:49
|
| Yes. When data is added, that query will have to wait for the expansion to occur. So you will see slow performance as the database file is growing. It shouldn't be too slow though as 10% is only 12MB right now.Tara Kizeraka tduggan |
|
|
|
Kristen
Test
22859 Posts |
Posted - 2006-06-13 : 02:06:55
|
| "We have an Application that has gotten extremely sluggish as of late"Did something else change on the machine at the time it started to get sluggish? Maybe the problem is elsewhereKristen |
|
|
|
DMcCallie
Yak Posting Veteran
62 Posts |
Posted - 2006-06-16 : 10:41:05
|
| Try this..dbcc updateusage (dbname) |
|
|
|
|
|
|
Truncating log