T-SQL Tuesday #53 – Why So Serious? No SQL Authentication Use Your Own Account

T-SQL Tuesday

At a previous job I had several developers that had passwords for SQL authenticated accounts for systems that would give them more access than they needed when they had Windows accounts that would give them enough to troubleshoot issues.  Our trick was to write a login trigger that would block any SQL Authentication accounts that were logged in with SSMS.  Many a developer fell pry to our logon trigger and because of the severity of the message did not quite understand why.  This made my troubleshooting life easy because I didn’t have to figure out if a developer ran something to fix something or if something legitimate was broke.  Of course I made sure to not block my sa account just in case I needed it.

Tracy Boggiano
Follow me

Tracy Boggiano

Database Administrator at ChannelAdvisor
Tracy has spent over 20 years in IT and has been using SQL Server since 1999 and is currently certified as a MCSE Data Management and Analytics. She has worked on SQL Server 6.5 and up including currently SQL 2017 CTP 2.0. She enjoys monitoring, performance tuning, and high availability and disaster recovery technologies. Tracy is currently a co-organizar the for special interest group for Advanced DBA Topics for the TriPASS user group.

She also tinkered with databases in middle school to keep her sports card collection organized.

Tracy has volunteered through the NC Guardian ad Litem program since 2003 advocating for abused and neglected foster children in court.This is her passion outside of SQL Server and favorite job.More information about this program in North Carolina can be found at http://volunteerforgal.org or the national organization CASA at http://www.casaforchildren.org.
Tracy Boggiano
Follow me