Comments
6 comments
-
Forgot to include I am using SQL 2008 R2 64bit on 64bit windows 7 enterprise if that makes a difference.
Microsoft SQL Server Management Studio 10.50.1617.0 -
Ok so after a restart/next day the script to alter gives me the correct results. (And an upgrade to 5.1.6.35)
So I guess to answer my own question is SQL Prompt will store the contents off all procedures from a specific point in time.
Another question might be how do I tell SQL Prompt it needs to update in this case? -
You can use either 'Refresh Cache' from the SQL Prompt menu or CTRL+SHIFT+D. See link below for more info.
http://www.red-gate.com/supportcenter/C ... .htm&p=SQL Prompt -
Perfect. Just what I was looking for.
As a side note it looks like the menu option was "Refresh Cache" but now listed as "Refresh Suggestions" as I cannot find a "Refresh Cache" option and "Refresh Suggestions" lists the keyboard shortcut "Ctrl+Shift+D" on the menu.
[Using SQL Prompt Version 5.1.6.35] -
Yes, you are correct sorry. That document was originally written for v3.9 and so is a little out of date.
-
Thanks again for the response.
My question/issue has been answered/resolved.
Add comment
Please sign in to leave a comment.
I thought these two features should work the same and reveal the same results?
I am using the same database and same stored procedure between SSMS script to alter and SQL Prompt script to alter.
SQL Search (1.0.0.342) actually searches and finds the stored procedure as it should be.
SSMS scripts the stored procedure to alter as it should be.
SQL Prompt 5 scripts the procedure to alter as it was previously this morning, but no longer. This is where I feel it is incorrect unless I have a miss-understanding of how this should work.
Anyone seen this before?
(There are other databases in my SSMS that have the same stored procedure. Could sql prompt be retrieving the procedure from the wrong database?)