Timeline for "Logon failed for login 'sa' due to trigger execution." When No SA Login Triggers Defined
Current License: CC BY-SA 4.0
9 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Jun 12, 2018 at 16:50 | comment | added | The Great Laughter | They do, yes. Could that be related? | |
| Jun 12, 2018 at 16:09 | comment | added | Alen | Do your apps use connection pooling? | |
| Jun 12, 2018 at 15:33 | comment | added | The Great Laughter | Aaron, there is no good reason for the 17 logon triggers, and I'll be consolidating them in the near future into just a single one. At the time, it was easier to create a new trigger per login, but that was a mistake. I've edited in the exact trigger, but it is generated based off of a template, so all the other triggers are the same. Is there value in posting all 17? Thanks | |
| Jun 12, 2018 at 15:33 | answer | added | David Browne - Microsoft | timeline score: 2 | |
| Jun 12, 2018 at 15:29 | history | edited | The Great Laughter | CC BY-SA 4.0 | added in full trigger |
| Jun 12, 2018 at 15:14 | comment | added | The Great Laughter | The server is not case sensitive. The triggers also do not insert anything to a table that doesn't exist (unless ORIGINAL_LOGIN() and APP_NAME() does), and I'd hope that the logins have access to those functions! EventData is also not explicitly used. Thanks though! | |
| Jun 12, 2018 at 15:12 | comment | added | Aaron Bertrand | We could make a bunch of guesses, but it would probably be better if you show all of your logon triggers, obfuscating any sensitive info of course, and explain why you need "a number of them." The most I've ever seen is 1. | |
| Jun 12, 2018 at 15:08 | comment | added | Kin Shah | is the server case sensitive ? have you check this support.microsoft.com/en-us/help/2002062/… ? | |
| Jun 12, 2018 at 14:52 | history | asked | The Great Laughter | CC BY-SA 4.0 |