06-29-2015 01:28 PM
I have a "RollbackSnapshotTempDB" is single user mode on a system with SQL2012 and SSR2013. I have tried the following with no luck. Any help would be appreciated
Step 1:
USE master
GO
ALTER DATABASE "RollbackSnapshotTempDB{XXX}"
SET OFFLINE WITH ROLLBACK IMMEDIATE
GO
Step 2:
DROP DATABASE "RollbackSnapshotTempDB{XXX}"
Step 3:
ALTER DATABASE DISTRIBUTION
SET MULTI_USER;
GO
07-01-2015 10:46 PM
Maybe this will help:
07-01-2015 10:49 PM
What's the actual problem related to SSR 2013? What's the error messag?
07-06-2015 08:22 PM
We rarely create scripts
07-14-2015 07:31 AM
I'm had a varation on the the problem described below ...
Its an interaction issue between SSR and MSSQL's VSS service. The variation in my case was that the I could not use the script identiified in the above link to delete the bogus Rollback DB. Since I wrote the above post I was able to delete the Rollback with the following steps.
Step 1
ALTER DATABASE "RollbackSnapshotTempDB{xxx}" SET SINGLE_USER WITH ROLLBACK IMMEDIATE
Step 2
sp_dbremove "RollbackSnapshotTempDB{xxx}"
Is there a Hotfix or patch to correct the creation of the bogu Rollback DBs?
07-15-2015 05:31 AM
What version of SSR are you running (check in Help -- About for specific version details) ?
07-15-2015 08:22 AM
SSR 2013 version 11.0.0.46600
also MSSQL 2012 SP1 - version 11.0.3128 (x64)
07-15-2015 08:25 AM
You need SP2 to get the fix - you don't have that.
If you look at my earlier reply, I did post details of the fix. Here it is again: