Tracing changes in SQL Server Stored Procedure
Hi all,
I'm looking for an easy way to track changes that are applied to Stored Procedures. At present developers at our site can modify stored procedures (as well as other objects) and we want to track when a modification is applied, and if possible also by whom. If it could be done to also trace what kind of changes were applied, that would be even better.
I've been looking into sp_trace_setevent procedures to trace object changes, but that's getting me nowhere.
Any idea's anyone ?
I'm looking for an easy way to track changes that are applied to Stored Procedures. At present developers at our site can modify stored procedures (as well as other objects) and we want to track when a modification is applied, and if possible also by whom. If it could be done to also trace what kind of changes were applied, that would be even better.
I've been looking into sp_trace_setevent procedures to trace object changes, but that's getting me nowhere.
Any idea's anyone ?
ASKER
Hi Winzig,
Are you actually using the LogExplorer ? I can't find any references to tracking changes in Stored Procecures in the online folders and documentation of LogExplorer. But if it can show me the changes, then my worries are over (for a couple of minutes at least!).
Thanks.
Are you actually using the LogExplorer ? I can't find any references to tracking changes in Stored Procecures in the online folders and documentation of LogExplorer. But if it can show me the changes, then my worries are over (for a couple of minutes at least!).
Thanks.
Never allow direct modification of stored procedures. Use scripts stored in SourceSafe (or another source control system), and always create your procedures with encryption on.
ASKER
Thanks Sjoerd,
But that's the main problem: there's no source control system installed, and historically every developer of the team can logon to SQLServer as 'sa', because they need to run system traces. I am in the process of proposing an important policy change, but these things take time, and in the meanwhile we can't track the changes made.
By the way, why using encryption ?
But nevertheless thanks for the valuable comment.
But that's the main problem: there's no source control system installed, and historically every developer of the team can logon to SQLServer as 'sa', because they need to run system traces. I am in the process of proposing an important policy change, but these things take time, and in the meanwhile we can't track the changes made.
By the way, why using encryption ?
But nevertheless thanks for the valuable comment.
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
you will be able track data, schema and permision changes :)