Login Failed

  • Comments posted to this topic are about the item Login Failed

  • The fact that there were any votes for the "delete Resource database" option was a bit scary.

    - Jeff

  • 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:

  • 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 😉

  • 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.

  • 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.

  • 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

  • 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