March 8, 2012 at 12:11 am
Hi All,
Can it is possible to edit the SQL Server security log??
If possible, please update how we can do...
Thanks in Advance.....
Satish
March 8, 2012 at 2:16 am
saidapurs (3/8/2012)
Hi All,Can it is possible to edit the SQL Server security log??
Satish
What do you mean by SQL Server Security Log ? And why do you want to edit it?
Usually security logs are there for auditing and by edting them you would make them more or less useless. But anyway, I really don't know what you mean with SQL Servers "Security" Log
[font="Verdana"]Markus Bohse[/font]
March 8, 2012 at 4:18 am
Hi Tunnel,
Just for cross verification, like if you connected my instance from your server that log will generate in my Error log files & even you have share access of my server for edit the log. So i want to know can it is possible to edit the log??..
Thanks
Satish
March 8, 2012 at 4:50 am
The SQL server transaction and error logs are not editable. They can be "read" in a fashion but not in an easily readable form.
Worth noting that successful logins are not logged by default.
March 8, 2012 at 7:56 am
saidapurs (3/8/2012)
Hi Tunnel,Just for cross verification, like if you connected my instance from your server that log will generate in my Error log files & even you have share access of my server for edit the log. So i want to know can it is possible to edit the log??..
Thanks
Satish
If you can edit them, they are not logs. Logs are there to track what actually happened. Editing the logs is what Haliburton did to their accounting books. The concept of editing logs is the same as trying to change history. You just can't do it. What is logged is a history of what happened.
_______________________________________________________________
Need help? Help us help you.
Read the article at http://www.sqlservercentral.com/articles/Best+Practices/61537/ for best practices on asking questions.
Need to split a string? Try Jeff Modens splitter http://www.sqlservercentral.com/articles/Tally+Table/72993/.
Cross Tabs and Pivots, Part 1 – Converting Rows to Columns - http://www.sqlservercentral.com/articles/T-SQL/63681/
Cross Tabs and Pivots, Part 2 - Dynamic Cross Tabs - http://www.sqlservercentral.com/articles/Crosstab/65048/
Understanding and Using APPLY (Part 1) - http://www.sqlservercentral.com/articles/APPLY/69953/
Understanding and Using APPLY (Part 2) - http://www.sqlservercentral.com/articles/APPLY/69954/
March 8, 2012 at 8:44 am
It is worth noting that you can in fact edit the SQL Server error logs, just not the currently active one. You can easily open them in notepad, make your changes and save them. The only evidence you have been in there is the modified date, which can also be changed.
A good reason to protect them if you are relying on them for auditing purposes.
Sincerely,
Dan B
March 8, 2012 at 8:49 am
MysteryJimbo (3/8/2012)
The SQL server transaction and error logs are not editable. They can be "read" in a fashion but not in an easily readable form.Worth noting that successful logins are not logged by default.
Like MysteryJimbo said, by default successful Logins are not registered in the SQL ErrorLog.
And yes you cannot edit the current errorlog because that file is in use, but if anyone has access and change permission on the folder containing the logfiles, he could edit older log files.
Is this what you're worried about? The just make sure you set your NTFS permissions correct and maybe also check the changed date of older the files.
[font="Verdana"]Markus Bohse[/font]
March 9, 2012 at 9:24 am
See this article on SSC to load the SQL Server error logs into a temp table for research (it does some deletes of certain records, so delete them only if you want, otherwise, leave them for research).
http://www.sqlservercentral.com/scripts/Error+Logging/70611/
Viewing 8 posts - 1 through 7 (of 7 total)
You must be logged in to reply to this topic. Login to reply