Comments
Sort by recent activity
It happens frequently enough that I wrote a very short (one line) batch file to delete all the files in "c:\users\<username>\appdata\local\red gate\sqlsearch 2\indexes\". When the problem occurs, I run the batch file then click Index -> Reindex on the SQL Search screen. Works every time. / comments
It happens frequently enough that I wrote a very short (one line) batch file to delete all the files in "c:\users\<username>\appdata\local\red gate\sqlsearch 2\indexes\". When the problem occurs, ...
Not to throw any water on the multi-server theory, but I am experiencing the same issue and, like IanC, I'm working with a single server and SQL Search Version 2.4.0.1203. The problem may be affecting clients with multiple server connections, but it most certainly is affecting those of us with single server connections, too. Please don't overlook is. / comments
Not to throw any water on the multi-server theory, but I am experiencing the same issue and, like IanC, I'm working with a single server and SQL Search Version 2.4.0.1203. The problem may be affect...
Hi Aaron,
Thank you for the advice! It was very helpful, and I was able to resolve the issue. You are correct, the problem had nothing to do with SQL Prompt. It was apparently coincidental that I observed the color-setting change after installing it. After uninstalling SQL Prompt, the problem remained. Attempting to reset all of the SSMS settings also caused the application to hang. I left the application in the hung-state for a few hours but it never became responsive. I tried repairing the installation but the problem remained.
Feeling adventurous (and a little desperate) I took a look at the registry. I found the settings for the results grid (HKEY_CURRENT_USERSOFTWAREMicrosoftSQL Server Management Studio11.0_ConfigFontAndColorsGridSQLResults) and deleted the Category and Package keys. The problem was resolved.
Thanks again for your help! My apologies for posting the problem here in the first place. Seems I was a bit hasty in my assessment of the underlying cause.
Jennifer / comments
Hi Aaron,
Thank you for the advice! It was very helpful, and I was able to resolve the issue. You are correct, the problem had nothing to do with SQL Prompt. It was apparently coincidental that ...