Comments
Sort by recent activity
fatherjack wrote:
Select pr.knownas, pr.surname from personnel as pr inner join personnel as pr2 on
aaaand the system locks. After a few minutes you can get in to the SSMS UI and slowly step by step select the query and delete it and then all returns to normal but it is a slow process as you have to wait for a very delayed response.
It seems to be having trouble gathering all the join options. The table has 368 columns... could be a problem if its trying to provide the cross join of all of those as possibilities?
If I do a query like that the suggestions come immediately, but the table I did a self join on only had 232 columns, maybe your extra 136 columns go over some limit?
Also, I am running 4.0.3.12, if you are really on 4.0.3.10 you might try upgrading. / comments
fatherjack wrote:
Select pr.knownas, pr.surname from personnel as pr inner join personnel as pr2 on
aaaand the system locks. After a few minutes you can get in to the SSMS UI and slowly step by ...
That is the snippet for "yell", an Easter egg of sorts that Red Gate put in... / comments
That is the snippet for "yell", an Easter egg of sorts that Red Gate put in...
I just confirmed that disabling SQL Prompt and re-enabling it causes it to refresh a portion of the cache.
It appears to clear the cache for the connected server, but not for linked servers. i.e. I was creating a query in DB1 that referenced tables in DB2, I added a table to DB2 and SQL Prompt didn't see it. After a disable/enable cycle SQL Prompt saw it.
On the other hand it didn't make SQL Prompt refresh the cache from a linked server DB, so it is only a partial solution. It appears the only way to completely refresh the cache is to restart SSMS. / comments
I just confirmed that disabling SQL Prompt and re-enabling it causes it to refresh a portion of the cache.
It appears to clear the cache for the connected server, but not for linked servers. i.e. I...
Brain,
If that is the way it is designed to work can I suggest that you add another option "Clear Suggestion Cache"?
It seems like a lot of unnecessary work if I am working on a query that uses 4 databases, and changes are made to objects in all of them that to get correct suggestions I either have to close SSMS and re-load everything and get back to where I was or:
* Refresh Suggestions
* Change current DB to DB2
* Refresh Suggestions
* Change current DB to DB3
* Refresh Suggestions
* Change current DB to DB4
* Refresh Suggestions
* Change current DB to DB1
If I am using a linked server and an object is updated on the remote server how can I refresh the suggestions? (I can't change the current DB to to the remote DB.) Is my only option to completely exit SSMS and then re-load everything? / comments
Brain,
If that is the way it is designed to work can I suggest that you add another option "Clear Suggestion Cache"?
It seems like a lot of unnecessary work if I am working on a query that uses 4 d...
It looks like if you go into options and disable SQL Prompt and then go back and enable SQL Prompt that the cache is cleared and SQL Prompt will refresh everything.
Can someone from Red Gate confirm that?
If so, I would think it should be fairly easy to give us a "Clear Entire Cache" option. Or at the very least put the Enable/Disable option back directly on the SQL Prompt 4 menu so we can toggle it quickly. / comments
It looks like if you go into options and disable SQL Prompt and then go back and enable SQL Prompt that the cache is cleared and SQL Prompt will refresh everything.
Can someone from Red Gate confir...
Essentially I expect "Refresh Suggestions" to completely clear the cache so that it was just like you started SSMS and SQL Prompt has to look everything up. / comments
Essentially I expect "Refresh Suggestions" to completely clear the cache so that it was just like you started SSMS and SQL Prompt has to look everything up.
It looks like this is fixed in the latest update, thanks! / comments
It looks like this is fixed in the latest update, thanks!
I have noticed this as well, but have never nailed it down to just being a problem in the SELECT portion of the statement. Hopefully they will get this fixed in the next release. / comments
I have noticed this as well, but have never nailed it down to just being a problem in the SELECT portion of the statement. Hopefully they will get this fixed in the next release.
Note: in the above example if you use the alias at line 2 first and leave it lower case, then when you use the alias at line 8 it is inserted as lower case, so the case appears to be coming from the first use of the alias, rather than where it should come from which is the definition of the alias. / comments
Note: in the above example if you use the alias at line 2 first and leave it lower case, then when you use the alias at line 8 it is inserted as lower case, so the case appears to be coming from th...
Anu Deshpande wrote:
Many thanks for your post Michael.
As per steps provided by you I tried to replicate the issue but it works fine for me.
Can you kindly email me the screenshot of the settings: SQL Prompt 4 --> Options --> Inserted Code --> Special Characters ?
I just sent the email to support@red-gate.com.
(Just for reference the options I have checked are:
* Add parentheses
* Single quotation mark
* Comment mark
* Square bracket) / comments
Anu Deshpande wrote:
Many thanks for your post Michael.
As per steps provided by you I tried to replicate the issue but it works fine for me.
Can you kindly email me the screenshot of the settin...