Active Formatting Style reverts to default after SSMS restart
fscottf
Posts: 4 Bronze 1
After upgrading SQL Prompt, the active Formatting Style reverts to the 'Default' setting each time I restart SSMS. The behavior occurs whether I select a 'Custom style' or a non-Default 'Redgate Style.'
No other intervening actions are needed to duplicate the issue. If I open SSMS, then immediately go to SQL Prompt > Options > Format/Styles > Edit formatting styles ... > Select 'Collapsed Style' (for example) > Set As Active > Close (button) > Ok (button) > Close SSMS > Open SSMS => style is set back to 'Default'
I've been using Redgate for about 3 years, and have kept current on all updates. And have used custom styles throughout that time without issue until this upgrade.
Thanks for any help!
Redgate SQL Prompt Version: 10.11.0.26431
No other intervening actions are needed to duplicate the issue. If I open SSMS, then immediately go to SQL Prompt > Options > Format/Styles > Edit formatting styles ... > Select 'Collapsed Style' (for example) > Set As Active > Close (button) > Ok (button) > Close SSMS > Open SSMS => style is set back to 'Default'
I've been using Redgate for about 3 years, and have kept current on all updates. And have used custom styles throughout that time without issue until this upgrade.
Thanks for any help!
Redgate SQL Prompt Version: 10.11.0.26431
SQL Server Management Studio 15.0.18390.0
SQL Server Management Objects (SMO) 16.100.46521.71
Microsoft Analysis Services Client Tools 15.0.19714.0
Microsoft Data Access Components (MDAC) 10.0.19041.1
Microsoft MSXML 3.0 6.0
Microsoft .NET Framework 4.0.30319.42000
Operating System 10.0.19043
Tagged:
Answers
Previously I had tried restarting SSMS, restarting the whole machine, Enabling/Disabling SQL Prompt suggestions, etc but with no luck. i.e. it would revert to the 'Default' style on each SSMS/system restart.
As for the logs, when I initially created this thread on Feb 7th, I had enabled Verbose Logging. However, there we no errors in the logs or anything else that indicated a problem. So, I don't think the logs would have helped much, even if I could reproduce the problem at this point.
One note, this Friday Feb 11th, I did run Windows 10 Updates which installed:
- 2022-02 Cumulative Update for Windows 10 Version 21H1 for x64-based Systems (KB5010342)
- 2022-02 .NET 5.0.14 Security Update for X64 Client (KB5011093)
Perhaps that update somehow fixed the problem?
Thanks.
No error message.
I have included 3 verbose logs, the first log is on startup.
The second after I set the active style to my custom style.
The third has after startup again.
Thanks