Comments
Sort by recent activity
Testing with synonyms and partial matching disabled I also get lags - if and only if IntelliSense is enabled as well (this is weird enough, since I wrote yesterday that I did not get lags when typing objects names from their beginning).
I am able to reproduce this on my client and on a server with SQL Prompt 6.1.0.40.
After install of 6.1.0.40 I manually copied my aliases from a backupped RedGate_SqlPrompt_Engine_EngineOptions.xml, since they were deleted again. / comments
Testing with synonyms and partial matching disabled I also get lags - if and only if IntelliSense is enabled as well (this is weird enough, since I wrote yesterday that I did not get lags when typi...
First of all: The new option for disabling synonym suggestions in GUI is working. When disabled, no synonyms are suggested anymore. Thanks, Aaron!
However, Beta 6.1.0.27 & .33 both reset various settings to defaults including aliases (all customizations are gone!), swap order in join clauses and others. Is this intended? @Lags:
Honestly, it's driving me nuts.
When disabling synonyms at the first time, it was lightning fast. Then I came to databases that showed lags again.
I realized that immediately after the lag my partial object string is red underlined by IntelliSense until I choose a suggestion (SSMS built-in auto-list members is off).
Hence, I turned off IntelliSense and the lags are gone. Until they reappeared after trying and trying again.
So I reenabled IntelliSense and synonym support in SQL Prompt and right now I do not have any lags.
What I also realized: When typing an object name from its beginning, there are never lags. Just when I type a partial match like "SELECT * FROM ite" when I want to get a suggestion for tDim_Item. / comments
First of all: The new option for disabling synonym suggestions in GUI is working. When disabled, no synonyms are suggested anymore. Thanks, Aaron!
However, Beta 6.1.0.27 & .33 both reset various se...
Database examples with lags:
TR 3
SQ 3
FN 10
S 67
D 1301
IT 6
PK 50
P 57
U 50
TF 1
SN 87
UQ 2
IF 1
V 202
SQ 3
FN 1
S 67
D 450
IT 6
PK 7
P 9
U 9
SN 103
V 86
TR 10
SQ 3
FN 5
S 67
D 702
IT 6
PK 33
P 47
U 33
C 5
SN 29
UQ 2
V 39
TR 8
SQ 3
FN 5
S 67
D 461
IT 6
PK 141
P 418
U 174
SN 158
UQ 5
IF 4
V 38
Database examples without lags:
SSISDB
PC 10
SQ 3
FN 11
TT 3
S 67
IT 6
F 28
PK 30
P 86
U 30
FS 4
TF 2
C 4
FT 2
UQ 4
V 33
ReportServer:
TR 7
SQ 3
S 67
D 8
IT 6
F 26
PK 31
P 236
U 34
C 3
UQ 1
IF 1
V 5
SQ 3
FN 1
S 67
D 43
IT 6
F 5
PK 33
P 42
U 33
V 41 / comments
Database examples with lags:
TR 3
SQ 3
FN 10
S 67
D 1301
IT 6
PK 50
P 57
U 50
TF 1
SN 87
UQ 2
IF 1
V 202
SQ 3
FN 1
S 67
D 450
IT 6
PK 7
P 9
U 9
SN 103
V 86
TR 10
SQ 3
FN 5
S 67
D 702
IT...
Aaron, would it be possible for you to provide your database to us? I would like to cross-check this issue with your database.
Concerning the option to turn synonym support off: They are still displayed in all databases regardless of the option turned off. / comments
Aaron, would it be possible for you to provide your database to us? I would like to cross-check this issue with your database.
Concerning the option to turn synonym support off: They are still disp...
6.1.0.27 is currently installed here. I closed SSMS several times now (e.g. during changing this option).
Our synonyms are pointing to other databases on the same instance as well as pointing to other instances running on different machines.
I just did a fresh install of SQL Prompt 6.1.0.27 on one of our servers, checked the lags and got lags (shorter, since the server is faster than my client).
Then I changed to <SynonymsEnabled>False</SynonymsEnabled> and tried another database on another server as before (to exclude possible caching): Lags again and the synonyms are still suggested. / comments
6.1.0.27 is currently installed here. I closed SSMS several times now (e.g. during changing this option).
Our synonyms are pointing to other databases on the same instance as well as pointing to ot...
So I keep it set to False. However, synonyms are still suggested (even in databases that I did not access for long time). Is there a way to manually purge this cache? Or is it purged at closing SSMS?
Until now, the setting does not seem to have an effect on my side. / comments
So I keep it set to False. However, synonyms are still suggested (even in databases that I did not access for long time). Is there a way to manually purge this cache? Or is it purged at closing SSM...
Aaron,
thanks for mentioning this option here. I discovered it by myself and changed it to false. However, synonyms are still in the suggestion lists. Why? Because they were cached?
This is why I did not write about it in my previous post. / comments
Aaron,
thanks for mentioning this option here. I discovered it by myself and changed it to false. However, synonyms are still in the suggestion lists. Why? Because they were cached?
This is why I d...
For compliance reasons: No
I just tested with various databases and there is a strong evidence that it has to to with synonyms. If there exist (many?) synonyms then I can reproduce those lags (it does not matter whether they point to another database on the local instance or to a linked server).
If I dropped all synonyms in this database, no lags occur (dropping just synonyms pointing to linked servers does not help). My test database contains 60 synonyms, that is very common in our environment.
My first guess was the count of objects in the considered databse, but it does not matter. SSISDB or other tool specific repository databases contain many objects and no lags occur (there exist no synonyms in SSISDB).
On those very few database containing no synonyms, I do not have any lags.
This is very surprising to me, since I obviously reported this issue since v5.3 that had no synonym resolution at all (though it suggested their names).
Aaron, could you test and reproduce this issue with databases containing a lot of synonyms?
I hope this helps! / comments
For compliance reasons: No
I just tested with various databases and there is a strong evidence that it has to to with synonyms. If there exist (many?) synonyms then I can reproduce those lags (it d...
Oh, so long ago? I must admit that I cannot remember the exact/first version anymore.
Btw, Partial Matching is great! It's ok to turn it off for testing as I did before. But permanently turning it off? That would not be our choice.
My test for disabled Partial Matching was just a single SELECT * FROM statement in a new query window. The first call of the suggestion objects lagged concerning key strokes. Succeeding calls within the same SELECT query do not lag. Adding another query causes lag again in this particular one (here again: just upon first call of suggestions). / comments
Oh, so long ago? I must admit that I cannot remember the exact/first version anymore.
Btw, Partial Matching is great! It's ok to turn it off for testing as I did before. But permanently turning it ...
We are also suffering from those lags with v6.
E.g. after typing SELECT * FROM the list of objects appears, but cursor key strokes lag several seconds in suggestion window.
But neiter setting <PartialMatchingEnabled> to false nor updating to 6.1 beta brought a solution. / comments
We are also suffering from those lags with v6.
E.g. after typing SELECT * FROM the list of objects appears, but cursor key strokes lag several seconds in suggestion window.
But neiter setting <Part...