Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase

Auditing All Activity Expand / Collapse
Author
Message
Posted Wednesday, December 17, 2008 11:46 AM


SSC Veteran

SSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC VeteranSSC Veteran

Group: General Forum Members
Last Login: Tuesday, January 14, 2014 4:18 PM
Points: 205, Visits: 641
Hi all,

I'm running into Level17 and Level19 errors when those have never been popping up in the past. I know that I haven't made any major changes to SQL Server and to be safe, I rolled back the changes that I did make to be sure those changes weren't the cause of the errors.

The errors are still popping up and the unique piece of this puzzle is a lack of transparency and openness. I have a supervisor that does things on his own and refuses to keep anyone in the loop. Furthermore, when I ask questions, I don't feel like I get straight answers.

So, the only way I'm going to know if something changes that I don't do (yes, I document my work) is if I audit all activity on the server.

Does anyone know of an efficient way to do this? Any help at all is greatly appreciated.

Thank you so much in advance.
Post #621516
Posted Wednesday, December 17, 2008 12:24 PM


Ten Centuries

Ten CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen Centuries

Group: General Forum Members
Last Login: Wednesday, July 16, 2014 8:13 AM
Points: 1,287, Visits: 1,837
for DDL.

from SSMS right click on db and select schema history changes report.


Alex S
Post #621540
Posted Wednesday, December 17, 2008 4:11 PM


SSCertifiable

SSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiable

Group: General Forum Members
Last Login: Yesterday @ 4:25 PM
Points: 5,563, Visits: 24,684
You might also want to try:
fn_trace_gettable

as:

SELECT *
FROM fn_trace_gettable
('C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\LOG\log.trc', default)

The location above is the default location for traces, yours may have been altered.


If everything seems to be going well, you have obviously overlooked something.

Ron

Please help us, help you -before posting a question please read

Before posting a performance problem please read
Post #621695
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse