What happens if you drop a user's default database in SQL Server 2005 and the user then tries to use SQL Server Management Studio? You get this crystal clear error message: What to do? If you have another working administrative login, then you simply need to use that to update the properties of the user that can't connect: But what if the user that can't connect is the only administrative user? In that case, you need to tell SQL Server Management Studio to connect to a different database on startup, ......