Thursday, October 10, 2013

[SQL Server] Who done it? Deleting Replication Jobs...

[SQL Server] Who done it? Deleting Replication Jobs...

Who done it? Deleting Replication Jobs...

Posted: 10 Oct 2013 02:16 PM PDT

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.

trying to KILL a SPID, getting 'Cannot use KILL to kill your own process.'

Posted: 10 Oct 2013 11:06 AM PDT

It's happening on an instance of SQL Server installed on my own machine. Inside a database called Sandbox, I was running a query that didn't want to finish, so I cancelled it. But, it appears it's still running cause when I do sp_who2 I get 54 RUNNABLE Domain MachineName . Sandbox SELECT INTO 31 33 10/10 17:00:06 Microsoft SQL Server Management Studio - Query 54 0 The SPID is 54 and when I try to kill it I get that error. So, I created another database login for the instance of SQL Serrver with sysadmin and public server roles checked and logged out as current user and back in with new login to kill the spid. Still can't. I've also rebooted. Still SPID 54 is there hogging resources and preventing me from updating a table on the Sandbox database.I need to kill the spid cause it's locking the resources on the database that I need. Not having access is ruining my evening plans.:w00t: How to solve this problem of SPID locking my database?NOTE: I am willing to take almost any action to solve this short of tossing the laptop, uninstalling SQL Server and reinstalling, deleting the whole database (cause it's not backed up, as it's been my sandbox).
Posted by at

No comments:

Post a Comment

Subscribe to: Post Comments (Atom)

Search This Blog