Activity overview
Latest activity by glennforum
CodantiM wrote:
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.
Seriously this is incredibly poor design. When you are developing a database you are constantly making changes and the fact there is no quick way to refresh ALL of the cache for SQL Prompt is really absurd.
I had to shut off SQL Prompt is just has become too annoying not having the information refreshed you have to wonder if RedGate even uses their products - this limitation becomes apparent in the first 5 minutes of use.
Overall for the money you pay for Redgate products you would expect not to have such a glaring limitation in one of their products.
Makes me just want to look for another vendor to spend my hard earned money with. / comments
CodantiM wrote:
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 lin...