How can we help you today? How can we help you today?
Manfred.Castro
Can you check that your graphics card drivers are up to date? This has been known to affect the performance of SQL Prompt. If you graphics card driver is up to date, It may be a case of SQL Prompt struggling with the number of columns in your databases. By default SQL prompt will attempt to cache all collumns of databases that you are connected to. Since the memory available to SQL Prompt is limited by SSMS, If you are connected to a large amount of databases or databases with a large amount of columns or a combination of the two it'll eventually fill up its cache of columns for suggestions, but most users don't ever hit that limit. If it does sound like it's just a case of too many columns, there's a few things you can do 1.) There's a config option in %LOCALAPPDATA%\Red Gate\SQL Prompt 5\RedGate_SqlPrompt_Engine_EngineOptions.xml called <MaxSupportedColumns> - you can use this to limit the size (in columns) of a database that SQL Prompt will load. If you set it, to, say, <MaxSupportedColumns>20000</MaxSupportedColumns>, SQL Prompt will give up on loading columns for databases with more than 20,000 columns. This is really to stop individual giant databases crashing Prompt. 2.) Sometimes just clearing the cache helps. Restarting SSMS will clear SQL Prompt's cache. So when SQL Prompt becomes sluggish you can try restarting ssms before it runs out of memory. 3.) Another option that may help is disabling linked server support in SQL Prompt. This will prevent SQL Prompt from attempting to provide suggestions from a linked server whose columns will be loaded into SQL Prompt's memory. / comments
Can you check that your graphics card drivers are up to date? This has been known to affect the performance of SQL Prompt. If you graphics card driver is up to date, It may be a case of SQL Prompt ...
0 votes