Did you know that ransomware is the most widespread, destructive malware in the world today? It accounts for 39% of all security breaches, with ransomware gangsters projected to make $11.5B in profits from online extortion by 2019.
SQL Server 2008 - Can't Drop DB
I have a database in SQL Server 2008 that I am trying, unsuccessfully, to delete. I open management studio, right click on the database, choose delete from the menu, and one of two things happens. One, SQL Server tells me that the database can't be deleted because it is in use or two, it "acts" as if it is going to work -- the "executing" wheel just spins and spins but nothing happens.
I've tried to use the following without success:
USE Master;
GO
DROP DATABASE dbname;
GO
I get the same results with that as with using the Delete pick from the menu.
I've also tried the following but it just tells me that the query is executing and it never stops
ALTER DATABASE MyDatabaseName
SET SINGLE_USER
WITH ROLLBACK IMMEDIATE
When I stop that query from executing, there are a bunch of lines in the output window which tell me "Nonqualified transactions are being rolled back. Estimated rollback completion: 100%".
I have stopped SQL Server and restarted it and I've stopped everything else that I can think could possibly connect to it. Any ideas?
I've tried to use the following without success:
USE Master;
GO
DROP DATABASE dbname;
GO
I get the same results with that as with using the Delete pick from the menu.
I've also tried the following but it just tells me that the query is executing and it never stops
ALTER DATABASE MyDatabaseName
SET SINGLE_USER
WITH ROLLBACK IMMEDIATE
When I stop that query from executing, there are a bunch of lines in the output window which tell me "Nonqualified transactions are being rolled back. Estimated rollback completion: 100%".
I have stopped SQL Server and restarted it and I've stopped everything else that I can think could possibly connect to it. Any ideas?
Who is Participating?
Experts Exchange Solution brought to you by
Enjoy your complimentary solution view.
Get every solution instantly with Premium.
Start your 7-day free trial.
I wear a lot of hats...
"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.
Thanks but I already tried that. As I mentioned above, when I get to the Alter Database part, the query just runs and runs and runs. If I cancel the query, the results area has line after line after line of the following:
Nonqualified transactions are being rolled back. Estimated rollback completion: 100%
Should I just let the query run? I'm not sure how long to let it run before I give up. Does DB size have anything to do with it? My DB is a little over 6GB.
Nonqualified transactions are being rolled back. Estimated rollback completion: 100%
Should I just let the query run? I'm not sure how long to let it run before I give up. Does DB size have anything to do with it? My DB is a little over 6GB.
I think this may help. If you run this all the processes should be killed, allowing you to then drop the database.
USE master;
GO
ALTER DATABASE YourDBName
SET SINGLE_USER
WITH ROLLBACK IMMEDIATE;
ALTER DATABASE YourDBName
SET MULTI_USER;
GO
USE master;
GO
ALTER DATABASE YourDBName
SET SINGLE_USER
WITH ROLLBACK IMMEDIATE;
ALTER DATABASE YourDBName
SET MULTI_USER;
GO
The problem is that the Alter Database ... Set Single User, once started, never stops running. It has run now for over an hour and 30 minutes (I just stopped it).
My guess is that it isn't working as intended. I'm certainly no expert though. Maybe I should just let it continue?
My guess is that it isn't working as intended. I'm certainly no expert though. Maybe I should just let it continue?
You need to let all the transactions complete. You can monitor to some extent what is going on by using sp_who. As soon as it completes and there are no connections to the database as eevidenced by sp_who, you should be able to drop the database.
The following query has been running now for 2.5 hours.
USE master;
GO
ALTER DATABASE YourDBName
SET SINGLE_USER
WITH ROLLBACK IMMEDIATE;
Is that normal? Should I just let it continue?
Also, do I run sp_who against the master db or against the db that I want to delete?
USE master;
GO
ALTER DATABASE YourDBName
SET SINGLE_USER
WITH ROLLBACK IMMEDIATE;
Is that normal? Should I just let it continue?
Also, do I run sp_who against the master db or against the db that I want to delete?
Problem Resolved!
I was connecting to the server using Windows authentication. When I connected using SQL Server authentication (SA user), I was able to drop the database by simply right clicking it and choosing delete from the menu.
Since I solved the problem, what do I do about awarding points on this one?
I was connecting to the server using Windows authentication. When I connected using SQL Server authentication (SA user), I was able to drop the database by simply right clicking it and choosing delete from the menu.
Since I solved the problem, what do I do about awarding points on this one?
Since I solved the problem, what do I do about awarding points on this one?
I find that odd to say the least and I suspect was just a coincidence. If you have permission to drop a database you can do it, otherwise you are out of luck. I suspect what was happening was that you were trying to drop the database while you were still in the same database. By changing to sa all you did was connect to a different database be default (probably master). In future, if you want to drop a database do it this way:
USE master
ALTER DATABASE [YourDatabaseName] SET SINGLE_USER WITH ROLLBACK IMMEDIATE
DROP DATABASE [YourDatabaseName]
Since I solved the problem, what do I do about awarding points on this one?
Select your comment as the solution
I find that odd to say the least and I suspect was just a coincidence. If you have permission to drop a database you can do it, otherwise you are out of luck. I suspect what was happening was that you were trying to drop the database while you were still in the same database. By changing to sa all you did was connect to a different database be default (probably master). In future, if you want to drop a database do it this way:
USE master
ALTER DATABASE [YourDatabaseName] SET SINGLE_USER WITH ROLLBACK IMMEDIATE
DROP DATABASE [YourDatabaseName]
Since I solved the problem, what do I do about awarding points on this one?
Select your comment as the solution
Experts Exchange Solution brought to you by
Your issues matter to us.
Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.
Start your 7-day free trialIt's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
Microsoft SQL Server
From novice to tech pro — start learning today.
Experts Exchange Solution brought to you by
Enjoy your complimentary solution view.
Get every solution instantly with Premium.
Start your 7-day free trial.
GO
ALTER DATABASE YourDBName
SET SINGLE_USER WITH ROLLBACK IMMEDIATE;
DROP DATABASE YourDBName
GO