Login Failures - from AD Accounts

  • Let say we have an AD Account and create a DB and this is the owner.

    DATABASE

    TRACEYDB(Owner AAC_MAIN\SUPERAPP)

    SERVICE (AAC_MAIN\SUPERAPP)

    (The SERVICE is a service account that runs on a web server or application level and uses this

    database).

    So what happens is the Database is deleted

    Delete TRACEYDB

    The error logs get filled up with

    (Error Logs AAC_MAIN\SUPERAPP) cannot access database TRACEYDB)

    Because it has not got the TRACEYDB and the SERIVICE has not been turned off.

    Anyway to monitor this - Almost like i have to run through the entire services and turn off

    these services when deleting a database.

    ---

  • Why would you be deleting a database that a service needs without first turning off the service?

  • Im just the DBA and get told to remove this Database and their developers don't turn off the services corresponding to it - i find out because is see the error in the log.

    So im looking at how to overcome this so im not filling up my logs with these invalid logins. I Can disable the service account but this will still come in as an error in the log cause it cannot access the DB.

  • You can setup a logon trigger and do a rollback if the login is the one you need to avoid 😉


    * Noel

  • Perhaps i have to write a script that checks failed login get the IP then go read this server and read all services that are running ...........that be interesting little windows script coming up .....

    Something to keep me entertained for a few good hours.

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

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