0

We are trying to get to the bottom of our issue. We have a service that connects as MyDomain\ServiceAdmin to a SQL 2008 database.

I believe we have just setup database mirroring too in case the DB/network goes down and we lose connectivity, but we most likely have not tested it.

We had various network issues and then maybe 30+ min later, the service failed and could not connect, saying "Login failed for MyDomain\ServiceAdmin" in the event viewer.

I connect to SQL and the server is running, the DB is there, but the user is not there under (DB>Security>Users) in SQL. Our DBA re-adds the user, and everything works.

DBA is pointing to network issues causing the problem and the user missing. Is that possible or are the network issues just a coincidence and he's trying to CYA?

1 Answer 1

2

DBA is pointing to network issues causing the problem and the user missing. Is that possible or are the network issues just a coincidence and he's trying to CYA?

I believe you have your answer.

4
  • Is there any way the mirroring had something to do with it? If perhaps they mirroring wasn't setup correctly?
    – Alex K
    Jun 13, 2012 at 17:49
  • Even if database mirroring is set up, it wouldn't randomly delete a single user unless that user was deleted in the first place on one of the mirrors.
    – Hyppy
    Jun 13, 2012 at 18:16
  • I'm being told that somehow the network failed and the SQL didn't see that account as existing anymore and automatically removed it from the database as an authorized user. Is that a load of smoke?
    – Alex K
    Jun 13, 2012 at 18:21
  • I feel like it is just smoke. There is nothing in MSSQL that should do this. I suppose there could be some custom routine that the DBA coded in, but it's doubtful. If this was the case, all other users from MyDomain should be gone as well.
    – Hyppy
    Jun 13, 2012 at 18:43

You must log in to answer this question.

Not the answer you're looking for? Browse other questions tagged .