![]() Even then, if you don’t quite know when the modification occurred, you could be looking for a virtual needle in the transaction log haystack.įortunately there is a solution to this problem. Generally the only way to go back and see if a stored procedure was altered or dropped would be to dig through transaction logs which can be very tedious, even with the assistance of some 3rd party tools. Tracking changes to database objects such as tables and stored procedures isn’t something SQL Server does natively.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |