Deleted DBs

  • Yesterday I created five DBs but someone dropped them in the night only. I am not sure who has done that. I shall be looking at the privileges soon. Anyway I have backups and I shall restore them. But I want to know whether master DB gives us information about the deleted DBs only or only current DB.

    -M

    -MJ
    Please do not print mails and docx unless it is absolutely necessary. Spread environmental awareness.

  • Just databases that are currently attached to the instance. If it was very recent, check out the default trace. It should have info on dropped databases. You'll find the .trc files for it in SQL's error log directory.

    Gail Shaw
    Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
    SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

    We walk in the dark places no others will enter
    We stand on the bridge and no one may pass
  • MichaelJasson (1/17/2009)


    Yesterday I created five DBs but someone dropped them in the night only. I am not sure who has done that. I shall be looking at the privileges soon. Anyway I have backups and I shall restore them. But I want to know whether master DB gives us information about the deleted DBs only or only current DB.

    -M

    In future purpose u can create DDL trigget to track them...and for now if ur default trace was running then use it for that.

    _____________________________________________________________________________________________________________
    Paresh Prajapati
    ➡ +919924626601
    http://paresh-sqldba.blogspot.com/[/url]
    LinkedIn | Tweet Me | FaceBook | Brijj

  • Thanks for this information to all... I shall always keep default trace running to avoid such happenings. Is this a good practice. Please let me know whether this is a good practice to run the default trace. Can this cause performance issues?

    -M

    -MJ
    Please do not print mails and docx unless it is absolutely necessary. Spread environmental awareness.

  • MichaelJasson (1/18/2009)


    I shall always keep default trace running to avoid such happenings.

    The default trace won't avoid such happenings. It'll only tell you who did it. The default trace (as it's name implies) is running by default. Unless you have a good reason, leave it running.

    Gail Shaw
    Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
    SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability

    We walk in the dark places no others will enter
    We stand on the bridge and no one may pass

Viewing 6 posts - 1 through 5 (of 5 total)

You must be logged in to reply to this topic. Login to reply