Comments
Sort by recent activity
I think you missed the point I did refresh the cache, but when I open a new query window it sometimes gets an old version of the cache that shouldn't exist anymore. / comments
I think you missed the point I did refresh the cache, but when I open a new query window it sometimes gets an old version of the cache that shouldn't exist anymore.
I would check to see how many lines you have SQL Prompt set to look at in your queries. (Under "Listed Candidates" -> "Performance")
It has options for the number of lines to process, and the number of variables to display in the list.
I work with very large queries, and I have had to set the option to have it scan the entire block even though it is slower.
Michael / comments
I would check to see how many lines you have SQL Prompt set to look at in your queries. (Under "Listed Candidates" -> "Performance")
It has options for the number of lines to process, and the numbe...
So even though the SELECT INTO code is gone, that query window remembers the structure of the SELECT INTO for the table over the real structure of the table?
I would expect the learned table info to get removed from memory when the SELECT INTO statement is deleted from the query.
I have also ran into cases where a query window has old cached information, even though the cache was updated and is correct in another query window. Is every windows cache separate for the same database?
Michael / comments
So even though the SELECT INTO code is gone, that query window remembers the structure of the SELECT INTO for the table over the real structure of the table?
I would expect the learned table info t...
No, that isn't how it works for me. (In 3.8.0.244)
Say you type this in a new query window:
SELECT *
INTO JunkSPT
FROM MASTER.dbo.spt_monitor
then you delete it, then you refresh the cache and type:
SELECT * FROM <cursor>
at that point it still suggests JunkSPT with the little red text next to it.
If the table actually exists in the DB it will be listed twice in the candidates once with the red text next to it (the INTO version) and once for the actual table. / comments
No, that isn't how it works for me. (In 3.8.0.244)
Say you type this in a new query window:
SELECT *
INTO JunkSPT
FROM MASTER.dbo.spt_monitor
then you delete it, then you refresh the cache and type...
Correct, I am referring to the yellow/green that SMSS puts on the left.
I just tried again and I couldn't replicate the issue.... / comments
Correct, I am referring to the yellow/green that SMSS puts on the left.
I just tried again and I couldn't replicate the issue....
Refreshing all before opening a SQL script didn't make any difference. It still takes around 6 seconds to load a script, even if I close the script and open the same one again. (It is 1500+ lines long.)
Michael / comments
Refreshing all before opening a SQL script didn't make any difference. It still takes around 6 seconds to load a script, even if I close the script and open the same one again. (It is 1500+ lines l...
Thanks, I didn't realize that I would need to re-activate to get the Pro features enabled. A side effect is that it de-activated SQL Dependency Tracker, which was included in the bundle we purchased. (It did add SQL Data Generator though.)
Michael / comments
Thanks, I didn't realize that I would need to re-activate to get the Pro features enabled. A side effect is that it de-activated SQL Dependency Tracker, which was included in the bundle we purchas...
I just upgraded to 3.8.0.244, and this is still sort of an issue, but it appears to be related to bad SQL.
If you put a -- in front of <cursor2> it doesn't capitalize not when you type it inside of the quotes. (I don't think it ever should anyhow.)
Also,
Try to type a single line comment with a ' in it. For example in a brand new query window:
--This view won't include all data
and you will end up with:
--This view won't include all data'
It added an extra ' trying to close the one I typed, but it shouldn't as it is in a comment.
Michael / comments
I just upgraded to 3.8.0.244, and this is still sort of an issue, but it appears to be related to bad SQL.
If you put a -- in front of <cursor2> it doesn't capitalize not when you type it inside of...
It doesn't look like this has gotten fixed in 3.8.0.244, and in fact if in a new query window you type: trun it doesn't even suggest TRUNCATE.
Michael / comments
It doesn't look like this has gotten fixed in 3.8.0.244, and in fact if in a new query window you type: trun it doesn't even suggest TRUNCATE.
Michael
I am running SQL Prompt 3.6.0.109, and I can't remember exactly what query I had that caused the suggestions to come up incorrect. If it happens again I will come back and post additional information.
Sometimes it is hard to supply examples that you can use, since you don't have the DB/table structure, and I can't always share the code. / comments
I am running SQL Prompt 3.6.0.109, and I can't remember exactly what query I had that caused the suggestions to come up incorrect. If it happens again I will come back and post additional informati...