Each time I open a query window for the first time in a new SSMS session on a certain production database, I get an error from SQL prompt telling me that it couldn't retrieve all the schema information due to a timeout expiring. I believe it has already most of the schema information, but might be hung up on a synonym that could be invalid (the last item in the SQL Prompt status window says something like "processing synonyms"). Dev and Test copies of the DB work just fine, though they are less busy and have fully resolvable synonyms.
Anyway, after I dismiss the error dialog I get no suggestions in for that query window at all. Of all the databases I work with, this is the one that I need the most help from SQL Prompt for - due to the support urgency of the queries I run there.
I'd like to know how I can configure SQL prompt to extend its timeout. In addition, is there a way to configure (or change SQL Prompt) to allow it to use the partially collected schema information to get some level of suggestions despite not having all synonyms, etc. in its cache.
Also, Is there a way I can see what SQL Prompt is trying to look at when it times out (tracing SQL on that server is not a good option for me) - that might give me an ability to isolate the offending object.
BTW, this happens in both SQL Prompt 5 and 6 in both SSMS 2008R2 and 2012.