Tek-Tips is the largest IT community on the Internet today!
Members share and learn making Tek-Tips Forums the best source of peer-reviewed technical information on the Internet!
-
Congratulations Chriss Miller on being selected by the Tek-Tips community for having the most helpful posts in the forums last week. Way to Go!
Analyze SQL log 1
- Thread starter JBaileys
- Start date
-
1
- #2
Lumigent has a product called Log Explorer which works pretty well. If you have no budget for this, you can try to use the DBCC LOG command, but that is undocumented (read unsupported by Microsoft). Outside of that, you are reduced to asking each person where they were on the night of the 4th ;-).
- Thread starter
- #3
I would have suggested Lumigent also....I've never used it but heard lots of great things about it. One caveat....it's my understanding that it can't read logs made prior to it being installed. Also, you can't use the eval version for a user database, it only works for Northwind and Pubs. Before you buy it, make sure it will be able to read a log that was created PRIOR to LogExplorer being installed.
-SQLBill
Posting advice: FAQ481-4875
-SQLBill
Posting advice: FAQ481-4875
We bought and installed Lumigent Log Explorer.
I think it's possible to explore logs taken before installation, so long as they are available e.g. extracted hourly to disk as part of a maintenance plan activity. What it can't do is relate spid's to user idents in logs from before installation (unless you have this recorded and can get the info into Lumigent database, but we never tried that). Lumigent has an option to record spid's and user idents, but we had problems with the quantity of data recorded. If the delete command/data is visible in Lumigent, it should be possible to get it back. However, if the data was truncated rather than deleted then it may not be possible.
In that case (or don't want to buy), you could try restoring a backup of the database (probably best to use another server), export the deleted table contents and then import, which is what we did in a similar situation.
I think it's possible to explore logs taken before installation, so long as they are available e.g. extracted hourly to disk as part of a maintenance plan activity. What it can't do is relate spid's to user idents in logs from before installation (unless you have this recorded and can get the info into Lumigent database, but we never tried that). Lumigent has an option to record spid's and user idents, but we had problems with the quantity of data recorded. If the delete command/data is visible in Lumigent, it should be possible to get it back. However, if the data was truncated rather than deleted then it may not be possible.
In that case (or don't want to buy), you could try restoring a backup of the database (probably best to use another server), export the deleted table contents and then import, which is what we did in a similar situation.
FYI:
Apex has a SQL Log tool that I like better than Lumigent and the demo version of that *can* hook up to a different db than Northwind or Pubs. I've never seen the RL version, just the demo, but I felt it was more expansive and intuitive than Lumigent's Log Explorer.
Just my .25 cents worth. @=)
Catadmin
Catadmin - MCDBA, MCSA
"The only stupid question is the one you *didn't* ask.
Apex has a SQL Log tool that I like better than Lumigent and the demo version of that *can* hook up to a different db than Northwind or Pubs. I've never seen the RL version, just the demo, but I felt it was more expansive and intuitive than Lumigent's Log Explorer.
Just my .25 cents worth. @=)
Catadmin
Catadmin - MCDBA, MCSA
"The only stupid question is the one you *didn't* ask.
- Status
Similar threads
- Locked
- Question
- Locked
- Question
- Locked
- Question
