Home > Archive > Microsoft SQL Server forum > July 2005 > How to check the last modifys in database









You are viewing an archived Text-only version of the thread. To view this thread in it's original format and/or if you want to reply to this thread please [click here]

 

Author How to check the last modifys in database
akej via SQLMonster.com

2005-07-24, 3:23 am


Hi everybody,

Is there way to check what were the last modifys to specified database??

I mean the last insertion, deletion ........... .. and in which tables.


Thanks for advance

--
"Imagination is more important than knolwege" (Albert Einshtein)


Message posted via webservertalk.com
http://www.webservertalk.com/Uwe/Fo...eneral/200507/1
Chandra

2005-07-24, 3:23 am

hi

you can check in the SQL Profiler.

best Regards,
Chandra
http://groups.msn.com/SQLResource/
http://chanduas.blogspot.com/
---------------------------------------

*** Sent via Developersdex http://www.droptable.com ***
Erland Sommarskog

2005-07-24, 3:23 am

akej via webservertalk.com (forum@webservertalk
.com) writes:
> Is there way to check what were the last modifys to specified database??
>
> I mean the last insertion, deletion ........... .. and in which tables.


No, there is no built-in support for this. Options to tackle this:

1) Your own autiding code.
2) Use Profiler.
3) Use a third-party product that works from the transaction log,
see www.lumigent.com and www.logpi.com for examples.


--
Erland Sommarskog, SQL Server MVP, esquel@sommarskog.se

Books Online for SQL Server SP3 at
http://www.microsoft.com/sql/techin.../2000/books.asp
akej via SQLMonster.com

2005-07-24, 7:27 am


Thanks for respone,

>2) Use Profiler.



can u plz explain me how to acomplish it using Profiler???

i'm newb and use for profiler only for checking for sp recompilation and so
on.

Thanks for help.



Erland Sommarskog wrote:
>
>No, there is no built-in support for this. Options to tackle this:
>
>1) Your own autiding code.
>2) Use Profiler.
>3) Use a third-party product that works from the transaction log,
> see www.lumigent.com and www.logpi.com for examples.
>


--
"Imagination is more important than knolwege" (Albert Einshtein)


Message posted via webservertalk.com
http://www.webservertalk.com/Uwe/Fo...eneral/200507/1
Erland Sommarskog

2005-07-24, 11:31 am

akej via webservertalk.com (forum@webservertalk
.com) writes:
>
>
> can u plz explain me how to acomplish it using Profiler???
>
> i'm newb and use for profiler only for checking for sp recompilation and
> so on.


You would have to catch the SP:StmtCompleted and SQL:StmtCompleted events,
and probably add some filters on it as well. You should trace to a file
or a table rather than to the GUI, so you can load the trace into a table
and analyse it later.

If it sounds messy, it is because it is - messy.

Personally, if I were to implement an auditiing scheme I would into some
3rd party product like Lumigent's Entegra (which works on the transaction
log) or Red Matrix's SQL Audit (which works ny triggers). I would not call
running a constant Profiler trace an adequate auditing solution, because
the information you get is too unstructures. Possibly one could write a
tool that reads the Profiler output and build some useful information
from that. But that is not a minor undertaking.

Profiler could be sufficient if you only need to answer the question
"who did last change X" may be every second month or so, and you are
prepared to spend an hour each time to dig up the answer.


--
Erland Sommarskog, SQL Server MVP, esquel@sommarskog.se

Books Online for SQL Server SP3 at
http://www.microsoft.com/sql/techin.../2000/books.asp
akej via SQLMonster.com

2005-07-24, 11:31 am


Tnx for replay,

can u plz explain me how to acomplish it using Profiler???


Chandra wrote:
>hi
>
>you can check in the SQL Profiler.
>
>best Regards,
>Chandra
>http://groups.msn.com/SQLResource/
>http://chanduas.blogspot.com/
>---------------------------------------


--
"Imagination is more important than knolwege" (Albert Einshtein)


Message posted via http://www.webservertalk.com
akej via SQLMonster.com

2005-07-24, 11:31 am


ok thanks now it's more clear


Erland Sommarskog wrote:
>
>You would have to catch the SP:StmtCompleted and SQL:StmtCompleted events,
>and probably add some filters on it as well. You should trace to a file
>or a table rather than to the GUI, so you can load the trace into a table
>and analyse it later.
>
>If it sounds messy, it is because it is - messy.
>
>Personally, if I were to implement an auditiing scheme I would into some
>3rd party product like Lumigent's Entegra (which works on the transaction
>log) or Red Matrix's SQL Audit (which works ny triggers). I would not call
>running a constant Profiler trace an adequate auditing solution, because
>the information you get is too unstructures. Possibly one could write a
>tool that reads the Profiler output and build some useful information
>from that. But that is not a minor undertaking.
>
>Profiler could be sufficient if you only need to answer the question
>"who did last change X" may be every second month or so, and you are
>prepared to spend an hour each time to dig up the answer.
>


--
"Imagination is more important than knolwege" (Albert Einshtein)


Message posted via webservertalk.com
http://www.webservertalk.com/Uwe/Fo...eneral/200507/1
Sponsored Links





Also available: Server administration forum archive | Web Design forum archive | Software forum archive | Hardware reviews archive | Programming forum archive

Copyright 2009 droptable.com