| So we have have a situation where, to get different release management items accomplished, we need to run SSMS as different users on the same machine. Myself - Normal development Release AD account - Running administrative tasks, etc. on production machines Backup Release AD account - Same as release but backup in case automated release password management on main release account gets screwed up. We have shortcuts tied to the other accounts using RunAs sans the password. We run the shortcut, enter the password and we're running SSMS under different credentials. SSMS Boost thinks there's no license associated with those release accounts. Normally, it's not an issue as I just get the nag screen. The problem finally rose to the tipping point when the default settings of SSMS boost prevented TRUNCATE statements from being run. I had to create two fake SSMS boost accounts so that I could activate SSMS boost to get to the settings. Was this the proper thing to do? Is there a simpler way? I didn't try re-using the activation code from my original account as I thought the code would be tied to the account under which the process was running. Thanks. |
 |
