July 13, 2009 at 9:12 pm
Comments posted to this topic are about the item Login Failed
July 14, 2009 at 7:20 am
The fact that there were any votes for the "delete Resource database" option was a bit scary.
- Jeff
July 15, 2009 at 12:54 am
pdanke (7/14/2009)
The fact that there were any votes for the "delete Resource database" option was a bit scary.
88 people opted this answer till now! :w00t:
July 15, 2009 at 1:37 am
Resource database is not wide known.
We belive in 4 system databases: master, model, tempdb, msdb.
For those who would delete resource database - remember, you have to restore your tempdb database from backup after that 😉
July 21, 2009 at 2:47 pm
Marcin Zawadzki (7/15/2009)
Resource database is not wide known.We belive in 4 system databases: master, model, tempdb, msdb.
For those who would delete resource database - remember, you have to restore your tempdb database from backup after that 😉
I thought SQL server would not work properly and have to re-install SQL Server.
SQL DBA.
July 21, 2009 at 2:49 pm
SanjayAttray (7/21/2009)
Marcin Zawadzki (7/15/2009)
Resource database is not wide known.We belive in 4 system databases: master, model, tempdb, msdb.
For those who would delete resource database - remember, you have to restore your tempdb database from backup after that 😉
I thought SQL server would not work properly and have to re-install SQL Server.
Ha HA........I got your sarcasm here. Good one. You cannot take backup or restore operation on tempdb.
SQL DBA.
March 21, 2010 at 3:34 am
It's a pity that the correct answer (login using DAC and set the default database and language for that login back to what they were before) isn't available.
I assumed the trigger concerned had a purpose - probably relating to corporate policy - and disabling as a quick fix would be unacceptable, also that I had followed good practise and backed up master before changing properties of a login, and since I wasn't allowed to pick the correct answer opted for what I still think is the least wrong of the options provided.
Tom
April 5, 2010 at 1:28 pm
You can also login using SQLCMD, then drop the trigger.
Logging in using SQLCMD bypasses the trigger, I have had to do it dozens of times when things go wrong.
/* ----------------------------- */
Tochter aus Elysium, Wir betreten feuertrunken, Himmlische, dein Heiligtum!
Viewing 8 posts - 1 through 7 (of 7 total)
You must be logged in to reply to this topic. Login to reply