Some of the most obvious things are often overlooked!
During one of my discussions with a client, I was asked for a simple way to detect all schema changes (DDL Operations) in the SQL Server database and to generate a report out of it. These people were interested in only the DDL operation performed and who performed it. To detect changes, they were planning to create a trigger, detect changes and then write it to a log file.
I advised them to use the Database Standard Reports which does the job for us
Open SSMS 2008 > Right Click a Database > Report > Standard Reports > Schema Changes History
The report displays you a history of all committed DDL statement executions within the Database
About The Author
Suprotim Agarwal, MCSD, MCAD, MCDBA, MCSE, is the founder of
DotNetCurry,
DNC Magazine for Developers,
SQLServerCurry and
DevCurry. He has also authored a couple of books
51 Recipes using jQuery with ASP.NET Controls and a new one recently at
The Absolutely Awesome jQuery CookBook.
Suprotim has received the prestigous Microsoft MVP award for nine times in a row now. In a professional capacity, he is the CEO of A2Z Knowledge Visuals Pvt Ltd, a digital group that represents premium web sites and digital publications comprising of Professional web, windows, mobile and cloud developers, technical managers, and architects.
Get in touch with him on Twitter @suprotimagarwal, LinkedIn or befriend him on Facebook
2 comments:
What privileges are required to generate this report? Can a user with DBO on that database generate the report? We are seeing an 'you do not have permission to run sys.traces' error. The sysadmin can run the report.
Most of these reports are internally calling a DMV. Check the 'Required Permission' section in this link over here Querying Dynamic Management Views. So you can run the profiler to check the DMV's being called and grant the SELECT permission to the user on that DMV.
Post a Comment