(Using ASE 15.7 SP110+) I have been exploring the use of global login triggers for a variety of purposes. I read that I had to be careful about inadvertently locking out "sa" and other necessary system-roled users. I could use specific, individual login triggers as well/instead, but would like the global option as a means of generically catching all login attempts to potentially write to my own, custom audit log.
I note that (non global) login trigger stored procedures "cannot be dropped" until/unless disassociated from login triggers. I tried an experiment with my global login trigger - wherein I removed the supporting stored procedure (without previously disassociating it from the global login trigger). Such immediately blocked all logins (including sa). Is that the intended behavior? Or is it an oversight - such that dropping the stored procedure supporting a global login trigger should not be allowed until disassociation from the global login trigger has occurred?
I look forward to reading your responses.
Thanks,
Ben Black