We have a requirement to block management studio connections for non sysadmins in SQL Server. This was implemented through a logon trigger and works fine. Last night the built in SQL Server maintenance plans (that run as an agent job)
failed due to the trigger. Once I disabled the trigger and traced the logon event in profiler, I see that these jobs that call the maintenance plans connect initially to SQL Server with a application name = 'SQL Server Management Studio' which is of
course blocked in my trigger. I was wondering if anyone knew why maintenance plans would be connecting as 'SQL Server Management Studio' when these maintenance plans are nothing more than SSIS packages?
Convert DTS to SSIS |
Document SSIS |
30+ SSIS Tasks |
Real-time SSIS Monitoring |
Quick Starts |
BI Blitz