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 |
|
PatDeV
Posting Yak Master
197 Posts |
 Posted - 2006-06-30 : 10:09:56
|
| I am getting this message in Log fileAutogrow of file 'templog' in database 'tempdb' cancelled or timed out after 109 ms. Use ALTER DATABASE to set a smaller FILEGROWTH or to set a new size.how can i solve it now!! Please helpI shrinked the tempdb to 1\2 g and the log is around 32 MB it also set to auto grow with 10% for both log and db.Thanks |
|
|
nr
SQLTeam MVY
12543 Posts |
Posted - 2006-06-30 : 10:26:58
|
| It's saying that it's timing out while trying to grow.It's having to grow because you did the shrink.32MB for the log mneans it will not grow by much at a time so sounds like you might have a disk problem.You can try setting a larger size for the log.==========================================Cursors are useful if you don't know sql.DTS can be used in a similar way.Beer is not cold and it isn't fizzy. |
 |
|
|
PatDeV
Posting Yak Master
197 Posts |
Posted - 2006-06-30 : 10:52:49
|
| no the space is available and there is enough space to grow too but it is not 32 MB but 32,345 KB and db file is around half a G. |
|
|
|
jen
Master Smack Fu Yak Hacker
4110 Posts |
Posted - 2006-06-30 : 11:07:10
|
| tempdb should not be shrinked, you may want to post this now to the data corruption forum--------------------keeping it simple... |
|
|
|
tkizer
Almighty SQL Goddess
38200 Posts |
Posted - 2006-06-30 : 13:50:03
|
quote:
Originally posted by PatDeV
no the space is available and there is enough space to grow too but it is not 32 MB but 32,345 KB and db file is around half a G.
Just because there's enough space for it to grow doesn't mean that this is not the problem. It probably isn't able to grow fast enough for the query. Do not shrink the tempdb database. There is a reason why it was at a larger size before.Tara Kizeraka tduggan |
|
|
|
Kristen
Test
22859 Posts |
Posted - 2006-07-01 : 06:06:34
|
| "set to auto grow with 10% for both log and db"Suggest you change that to a fixed size for autogrow - maybe 50MB - once you get into multi-GB database size a 10% extension can take long enough that it causes timeouts left, right and centre!Set the initial size to something appropriate for your configuration - e.g. the size you normally see it operating at. No sense a server restart creating a 1MB TEMPDB, and then extending it by 10% (or even 50MB for that matter) all the way up to multi-GB sizes!)DO NOT SHRINK TEMPDB - NOT EVER. REPEAT. DO NOT SHRINK TEMPDB. Stop-Start the SQL Service if you really need to kill of an exceptional-oversize TEMPDB.And if you really REALLY need to avoid that advice and Shrink TEMPDB then read up on all the EXCEPTIONAL precautions you need to take to prevent database corruption. It really is THAT bad!Kristen |
|
|
|
Michael Valentine Jones
Yak DBA Kernel (pronounced Colonel)
7020 Posts |
Posted - 2006-07-01 : 15:38:04
|
quote:
Originally posted by PatDeV
no the space is available and there is enough space to grow too but it is not 32 MB but 32,345 KB and db file is around half a G.
32 MB and 32,345 KB are almost the same.select MB, KB, Retio = KB/MBfrom (select MB=32*1024*1024.,KB=32345*1024. ) aResults:MB KB Retio----------------- ------------ -----------------33554432 33121280 .9870910644531250 CODO ERGO SUM |
|
|
|
|
|
|
tempdb error!! urgetn!!