Tag Info

New answers tagged

2

You can use the Power of Default Trace to find out the culprit. provided the default trace files are not rolled over -- find out the default trace location SELECT * FROM fn_trace_getinfo(default); GO --- check the events SELECT TextData, HostName, ApplicationName, LoginName, StartTime FROM [fn_trace_gettable]('Location of ...


1

Shrinking information is not logged in errorlog as such. Are you talking about log file size or data file size or complete SQL database size? All three are different. There can be many reasons for a database size decrease. A few are, Somebody took a log backup and shrank the log file. Somebody deleted lots of data from SQL server table and run shrink ...



Top 50 recent answers are included