Save your settings in a shared folder you want to use (a network share or Dropbox folder, for example) by clicking Save as., changing the file location and clicking Save.In the menu bar select SQL Prompt → Manage Code Analysis Rules.If the problem persists, enable verbose logging, reproduce the issue, log a ticket with Support and attach the log file for further investigation.You can share your Code Analysis rules settings with other SQL Prompt users by saving them in a shared folder (for example a Network share or a Dropbox folder). Please see here for troubleshooting steps. Note: If it's Object Explorer that's slow, this is more likely caused by SQL Source Control. If the slowness occurs on startup, try disabling Tab History (SQL Prompt > Options > Tabs > History > Enable Tab History).If your SSMS version is below 17.3, you can raise the amount of RAM available for SSMS by using the Large Address Aware utility on ssms.exe (see ).Disable the auto-refresh experimental feature (SQL Prompt > Options > Labs > Experimental features).
Go to SQL Prompt > Options, click on Export to save your settings, and then try a "Restore all defaults".Disable the built-in intellisense under Options > Text Editor > Transact-SQL > Intellisense.Disable Code Analysis function (SQL Prompt > uncheck “Enable Code Analysis”) and test again if the problem disappears, it suggests that "Code Analysis" is the culprit, so please contact Support.Set the snippets folder to a local path in case there is a network issue reaching the remote path that has been set up previously.Clear the cache by disabling SQL Prompt > Enable Suggestions and re-enable it again.If the problem persists with the latest version (Help > Check for updates), please try the following steps: To isolate the problem, please uninstall SQL Prompt and test if SSMS is still slow.
0 kommentar(er)
