October 10, 2013 at 9:16 pm
I have a vendor that keeps deleting my replication job. Before my company will address the issue, I have to proof who done it. I'm 99% sure they used sp_removedbreplication. Any ideas where I can find this information in SQL? I REALLY REALLY want to catch this vendor red handed.
October 15, 2013 at 10:27 am
This would be BLIND shot... but see who logged in just before the replication started getting failed.but SEE ... there are 100 % chances that the login who deleted the job could have logged in a long time ago.:-)
-------Bhuvnesh----------
I work only to learn Sql Server...though my company pays me for getting their stuff done;-)
October 21, 2013 at 3:47 am
If you are doing this type of forensics, then IMHO this justifies changing a system stored procedure for the duration of the investigation.
Look at the source of sp_removedbreplication and add code that will log the connection details of who uses it into a table.
Remember to revert back to the standard MS code when you have finished...
Original author: https://github.com/SQL-FineBuild/Common/wiki/ 1-click install and best practice configuration of SQL Server 2019, 2017 2016, 2014, 2012, 2008 R2, 2008 and 2005.
When I give food to the poor they call me a saint. When I ask why they are poor they call me a communist - Archbishop Hélder Câmara
February 25, 2014 at 12:58 pm
I was able to track down the cause of the replication job disappearing. The development team was dropping and recreating the database from a previous backup that did not have the replication switch applied. This caused a mess with Replications.
However, I did modify the system stored procedure in our dev environment to log who done it.
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply