Eric M Russell (4/24/2014)
If a software application is hard coded to use the "SA" account, you can rename it and then create a new account named "SA" with limited permissions. One or more builtin database level roles like db_ssisadmin, db_datareader, or even db_owner can provide all the permissions it requires to function. This also works for environments where developers and the BI team have been using the "SA" account for years. Don't tell them, just do it. So long as they can still select from tables and view schema, they probably won't know the difference.
Wow. + 1000000 if not more and this month's Evil Genius Using Their Power For Good Award
I'm a DBA.
I'm not paid to solve problems. I'm paid to prevent them.