The Lounge is rated Safe For Work. If you're about to post something inappropriate for a shared office environment, then don't post it. No ads, no abuse, and no programming questions. Trolling, (political, climate, religious or whatever) will result in your account being removed.
I feel like I'm in the middle of a Seinfeld episode where a simple miscommunication leads to disaster. I was on a phone call with a client's dba explaining once again how the sql authentication method she had selected was causing problems for the end users. (desktop app)The options were sql server login or integrated...she chose integrated using a dedicated domain account meaning that the application has to run in the context of that dedicated account for the connection to work. (or am I missing something) Unfortunately, this causes other problems...too much to get into with this post.
Anyhow, after a few minutes of explaining things, she (the dba) gasps and cries out 'Why me? Why me? What have I done in life to deserve this?' Feeling more than slightly offended, before my filter could kick in I uttered 'Yeah, Karma's a bit@h.' Maybe it was a VOIP glitch on one end or the other, but the only word she heard was the last one and hung up! My boss was present and heard the whole thing so I'm not too worried about the not so nice email just now from her boss asking for an accounting of events and an apology. Yep, Karma's a bit@h! No more coding this afternoon for me! I'm in timeout!
Thank you! The dba in question is in fact a 'fresher'. They taught her in school that sql server authentication is evil. The irony is that the tech doing the installs saved the domain account credentials out on the network in a text file since there was no way he was going to be able to remember the 20+ character gibberish password for future installs. I've submitted my apologies and recommendations to all parties involved, including her boss. If we can't reach an understanding, I can always demote the customer to Access!