how do i find out what process could have caused a transaction log to fill
up possibly over hte last 24 or 48 hours?
thanks in advance
up possibly over hte last 24 or 48 hours?
thanks in advance
-
-
Re: transaction log
lark (lark@buysureth ing.com) writes:You can try DBCC LOG and see if you can make some sense of the output.how do i find out what process could have caused a transaction log to fill
up possibly over hte last 24 or 48 hours?
I think the first parameter is the database id, and the second controls
the amount of output.
Else, you need a log reader. There are a couple on the market. Lumigent
have been in that trade the longest. There is also Log PI, and I think
ApexSQL has one too.
But if your transaction log fills up in 48 hours, you are probably not
backing it up often enough. Depending on your recovery needs, once an
hour, or every ten minutes may be good choices.
--
Erland Sommarskog, SQL Server MVP, esquel@sommarsk og.se
Books Online for SQL Server 2005 at
Books Online for SQL Server 2000 at
-
Re: transaction log
"Erland Sommarskog" <esquel@sommars kog.sewrote in message
news:Xns9AD55DC 3D077Yazorman@1 27.0.0.1...lark (lark@buysureth ing.com) writes:>>how do i find out what process could have caused a transaction log to
>fill
>up possibly over hte last 24 or 48 hours?
You can try DBCC LOG and see if you can make some sense of the output.
I think the first parameter is the database id, and the second controls
the amount of output.
>
Else, you need a log reader. There are a couple on the market. Lumigent
have been in that trade the longest. There is also Log PI, and I think
ApexSQL has one too.
>
But if your transaction log fills up in 48 hours, you are probably not
backing it up often enough. Depending on your recovery needs, once an
hour, or every ten minutes may be good choices.
>
>
--
Erland Sommarskog, SQL Server MVP, esquel@sommarsk og.se
>
Books Online for SQL Server 2005 at
Books Online for SQL Server 2000 at
http://www.microsoft.com/sql/prodinf...ons/books.mspx
thanks erland.
Comment
Comment