Click here to monitor SSC
SQLServerCentral is supported by Redgate
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase

Who done it? Deleting Replication Jobs... Expand / Collapse
Author
Message
Posted Thursday, October 10, 2013 9:16 PM
Grasshopper

GrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopper

Group: General Forum Members
Last Login: Thursday, August 27, 2015 3:22 PM
Points: 19, Visits: 159
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.
Post #1503855
Posted Tuesday, October 15, 2013 10:27 AM


SSCrazy

SSCrazySSCrazySSCrazySSCrazySSCrazySSCrazySSCrazySSCrazy

Group: General Forum Members
Last Login: Tuesday, July 19, 2016 4:34 AM
Points: 2,850, Visits: 4,076
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
Post #1504853
Posted Monday, October 21, 2013 3:47 AM This worked for the OP Answer marked as solution
Hall of Fame

Hall of FameHall of FameHall of FameHall of FameHall of FameHall of FameHall of FameHall of FameHall of Fame

Group: General Forum Members
Last Login: Tuesday, August 30, 2016 2:28 AM
Points: 3,034, Visits: 3,711
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: SQL Server FineBuild 1-click install and best practice configuration of SQL Server 2016, 2014, 2012, 2008 R2, 2008 and 2005. 29 Aug 2016: now over 38,000 downloads.
Disclaimer: All information provided is a personal opinion that may not match reality.
Quote: "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
Post #1506596
Posted Tuesday, February 25, 2014 12:58 PM
Grasshopper

GrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopperGrasshopper

Group: General Forum Members
Last Login: Thursday, August 27, 2015 3:22 PM
Points: 19, Visits: 159
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.
Post #1545121
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse