[Last Call] Learn how to a build a cloud-first strategyRegister Now

x
  • Status: Solved
  • Priority: Medium
  • Security: Public
  • Views: 283
  • Last Modified:

SQL Server logs - how to find out what happened and when

Hi,

One of our production databases has been altered over the weekend. In particular a table containing user data has been updated across the board, altering usernames. This should not have happened and we are trying to find out when it happened and who did it.

Our regular DBA is not here and although I do SQL Server DB development I'm not sure what can be done in this situation. It seems like the database and transaction logs have only been retained for the past two days so the oldest available backup includes the unwanted changes committed.

Is there any way to find out when these updates occurred and under what credentials this happened?

Thanks.
0
irb56
Asked:
irb56
1 Solution
 
gplanaCommented:
Do you mean error logs ?

Please see this link: http://msdn.microsoft.com/en-us/library/ms187885.aspx
0
 
irb56Author Commented:
Thanks for the link but these are not errors we're trying to identify, they are committed update transactions on a particular table. I've done a bit of searching, which so far has lead me to download a trial of a log reader named ApexSQL Log. I believe this is supposed to allow you to audit database changes, including seeing details of the transaction(s) that updated the table in question and the associated login info, etc.

However, I am unsure what the limitations of such a tool will be. How far back can you go in the auditing?
0
 
gplanaCommented:
It depends of your logs. You can go until last checkpoint, which is a point where logs are synchronized with data. For example, in Oracle there is a mode called "archive logs" which permits to have all logs archieved, so you can go virtually to any passed time.

I don't think SQL-server has this functionality, but you can use DTS. See this: article: technet.microsoft.com/en-us/library/bb687457.aspx
0
Technology Partners: We Want Your Opinion!

We value your feedback.

Take our survey and automatically be enter to win anyone of the following:
Yeti Cooler, Amazon eGift Card, and Movie eGift Card!

 
irb56Author Commented:
It looks like the ApexSQL Log tool is excellent. As well as identifying the details of every change, it provides a facility for automatically generating scripts to reverse the change.

I assume there are other SQL Server log reader tools out there. Does anyone have any recommendations, particularly if there are any useful products that don't cost as much as ApexSQL?

Also I am curious regarding the limits of a log reader tool. How is it affected by the database recovery model and the frequency and types of backup? For example, if a database has the full recovery model and both database and log file gets backed up, doesn't this truncate the log file and would this mean that those transactions truncated from the log file would then become unavailable to the SQL log reader tool?
0
 
Ramesh Babu VavillaCommented:
use xp_readerrorlog command in the management studio, you will get the error log
0
 
Anthony PerkinsCommented:
>>use xp_readerrorlog command in the management studio, you will get the error log<<
Pray tell what in the world has that got to do with the Transaction Log?
 
0
 
irb56Author Commented:
Thanks for your help. :-)
0

Featured Post

Concerto's Cloud Advisory Services

Want to avoid the missteps to gaining all the benefits of the cloud? Learn more about the different assessment options from our Cloud Advisory team.

Tackle projects and never again get stuck behind a technical roadblock.
Join Now