Activity overview
Latest activity by Ar4i
Not getting a popup immediately is definitely better than everything freezing for a few seconds on every keystroke even when just moving the cursor with arrows and mouse. Maybe you could avoid doing any parsing while just moving around and not typing? With the official beta version it freezes even when clicking to open a menu.
Other than that, so far this version works pretty well.
P.S. Expand wildcards seems to be CASE SENSITIVE thats why it isn't working in some cases, our databases are CI. Thats true for other functions as well and let to the confusion that there is a problem in SPs with declared and temporary tables. / comments
Not getting a popup immediately is definitely better than everything freezing for a few seconds on every keystroke even when just moving the cursor with arrows and mouse. Maybe you could avoid doin...
There are only INFO messages in the log, no errors or warnings.
I've uninstalled Prompt 5 and installed the above unstable release and it is now working a lot faster at least during the short test I managed to do. There is a minimal lag when displaying suggestions, but the real big lag on every key press seems to be gone - which is great.
I did notice however that when I open a stored procedure there aren't automatic suggestions ([ctrl+space] works). While if I start a new script, suggestions do pop up automatically.
However there is still lag when browsing the object explorer which is not critical.
It is a bit out of topic, but are functions "expand wildcards" and "qualify object names" supposed to work within stored procedures, functions and triggers and especially with temporary tables and table declarations? They don't seem to work in this version.
I'll try using this version for a few days to see how it performs. / comments
There are only INFO messages in the log, no errors or warnings.
I've uninstalled Prompt 5 and installed the above unstable release and it is now working a lot faster at least during the short test ...
We have installed it on several brand new clean PCs (Prompt 5.3.8.2 pro) and our databases are completely unrelated and different than the ones of LSZ (although they seem to be of a similar complexity), still SQL Prompt seems to work the same way. Everyone of my colleagues already uninstalled it.
I'll download and try the above version, although I'm not aware of the licensing policy of your company and I don't know if we are going to able to use it once it is a final product. Unfortunately the version we bought seems to be useless for us at the moment. / comments
We have installed it on several brand new clean PCs (Prompt 5.3.8.2 pro) and our databases are completely unrelated and different than the ones of LSZ (although they seem to be of a similar complex...
Manfred.Castro wrote:
Can you check that your graphics card drivers are up to date? This has been known to affect the performance of SQL Prompt.
Installed the newest version - no change.
Manfred.Castro wrote:
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.
We have no individual giant databases, we work 99% of the time with databases with exactly the same structure.
Manfred.Castro wrote:
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.
It is extremely "sluggish" right from the start.
Manfred.Castro wrote:
3.) Another option that may help is disabling linked server support in SQL Prompt.
There are no linked servers.
I've tried with a small database (1800 columns) and it runs ok, but with our production databases it is unbearable.
If that has anything to do with the problems - we are using one big schema, because our database structure exists way before schemas were even introduced in SQL Server. The "sluggish behavior is present even when browsing the DB structure in object explorer. / comments
Manfred.Castro wrote:
Can you check that your graphics card drivers are up to date? This has been known to affect the performance of SQL Prompt.
Installed the newest version - no change.
Manf...
SQL Prompt 5 working very slow on SSMS 2012
Having code suggestions enabled in SQL Prompt 5 menu makes editing in SSMS work very slow even on a relatively small scripts (like 50-100 lines). On larger scripts it is completely unusable.
It is ...