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 |
|
colinbun
Starting Member
3 Posts |
Posted - 2002-02-13 : 04:53:09
|
| Hi there.A number of times now our tempdb or its transaction log has filled up, and the only recovery I'm aware of is to restart SQL Server's services. We are constrained by our software suppliers who have told us to set the size of these two files and take off the options to allow the files to grow automatically.Are there any tools you are aware of that allow us to look into transaction logs to see what is taking up the space (I know how to look into the tempdb itself), in terms of either procedure/table updates/spid?Cheers,Colin |
|
|
efelito
Constraint Violating Yak Guru
478 Posts |
Posted - 2002-02-13 : 09:58:11
|
| Log Explorer (http://www.lumigent.com/Products/index.htm) can be used to look into and replay transaction logs, but I don't think it will work for tempdb. Filling the transaction logs in tempdb is usually not an issue, unless the application is running huge transaction or for some reason the truncate log on checkpoint database option has been unchecked. I would make sure the db has this option checked and/or expand the tempdb and log.Jeff BanschbachConsultant, MCDBA |
 |
|
|
izaltsman
A custom title
1139 Posts |
Posted - 2002-02-13 : 18:20:10
|
| Have you tried DBCC OPENTRAN (tempdb) to see if there is a process holding an open transaction in tempdb for an excessively long period of time? |
 |
|
|
colinbun
Starting Member
3 Posts |
Posted - 2002-02-15 : 05:37:27
|
| Fantastic! The dbcc onpentran(tempdb) command gives me a bit more information, and I'm evaluating the Lumigent product. It looks what I want for the moment, so we shall see.Many thanks for the help,Colin |
 |
|
|
|
|
|