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 |
|
TRACEYSQL
Aged Yak Warrior
594 Posts |
 Posted - 2006-08-26 : 08:18:20
|
| I have tempdb that grews sometimes to whole sizes 118 gig over weekend.With these tools below is that reading the LDF files.and does it cause any problem using these tools whilst activity running.If i got one of these i be able to see whats going on in tempdb and why it so big?Get Log Explorer from Lumigent:http://www.lumigent.com/products/le_sql.htmlRed Gate also has a log reading product:http://www.red-gate.com/products/SQL_Log_Rescue/index.htmThere's also the DBCC LOG command. It is undocumented though, and the output is not easily readable. Log Explorer would be your best bet. |
|
|
TG
Master Smack Fu Yak Hacker
6065 Posts |
Posted - 2006-08-26 : 09:53:38
|
| I'm not confident that the log reader tools will help you solve your problem. I think the most likely cause is an unintentional long running open transaction. This could be caused by a large query with an unintended cross join / cartisian product (especially if there is an ORDER BY or GROUP BY in the statement), or an explicit begin transaction that was never committed or rolled back. That could be a simple oversight or the result of a code error or contention collision that halted execution leaving the transaction open. Or perhaps loosing track of nested transactions.One way to identify a possible culprit is to see what new code was introduced about the time the problem started. Pehaps look at dbcc opentran restults to see if there is anything unusual.I don't believe you can set tempdb to any recovery model other than simple, isn't that right my dba friends?Be One with the OptimizerTG |
 |
|
|
|
|
|
Reading Log files