I somehow managed to get a database object with an empty name into one of my instances of SQL Server. I can't delete it or otherwise work with it (I've tried renaming it so I could delete it) without getting an error message because of the empty name. I've tried these things (as well as a "Drop Database" query with no name, which I didn't expect to work and it didn't) from both the SQL 2000 and 2005 environments. Has anyone come across this before? I don't suppose this database is hurting anything but I'd still like to get rid of it. The objects in it make it appear to be a copy of the Master database - it also doesn't show up where I would expect it to in the Data folder for this instance.
Thanks,
Dave
Dave,
I never come across this problem. Whenever I have to drop or delete a database, I relatively get that done with ease. In case the database name is empty, which is very weird case, I will suggest you to try deleting using Enterprise manager. It would have been more easy to address your issue if you could specify what error message did you get when you tried renaming or using "Drop Database" query. But I am pretty sure you can delete your database using Enterprise Manager. However, you have to make sure before deleting your database that the database is not currently running. Most easy way to do that is to stop the Sql Server Service Manager from your task bar.
I hope it works.
Ujjwal Kaji
|||Thanks for the reply. I tried deleting it in Enterprise Manager and get the same Error Message:
Error 21776: [SQL-DMO]The name '' was not found in the Databases collection. If the name is a qualified name, use [] to separate various parts of the name, and try again.
Thanks for any insight into this.
-Dave
|||Hi,
before messing with the system tables, try to do a:
1. DROP DATABASE []
2. sp_renamedb '','MyDatabasetoDelete'
or (posted by Tom Moreau)
3. (can vary to SQL server 2k5, because sysdatabases is sys.databases now)
sp_configure 'allow', 1
go
reconfigure with override
go
update sysdatabases
set
name = 'MyDB'
where
name = ''
go
sp_configure 'allow', 1
go
reconfigure with override
go
Stop and start SQL Server.
Check after each steps if the database is till existing, sometime SQl Server doesn′t know how to handle return code for this strange situation and gives back a weird error.
HTH, Jens Suessmeyer.
http://www.sqlserver2005.de
|||Jens,
Thanks for the reply. I guess somehow it was a system database because your 3rd suggestion worked perfectly. Very strange...
Thanks for your help.
Dave
|||Thank you for the post, option 3 solved my empty database name as well.