Activity overview
Latest activity by Eric
I may have skipped the last beta. From what I remember when I tried it I just added the path of the Compact db in the exclusion tab.
After I installed the release on a developer's desktop working with both Compact and Std, he complained he had to deactivate SQL Prompt. When I went to configure it the same what I had done with the beta, it seemed to me the server/db dialog was not what I had seen with the beta. There's been a couple of months between the 2 incidents, so I am not sure.
I tested the beta with SQL Compact (in november or december) and, at your suggestion, I added the exclusion path and it worked. When we installed the release we could not make it work anymore.
We've bought a bunch of serials but only a few of us work regularly with SQL Compact and that specific developer speaks a couple of languages but only 3 words of english [image] so he asked to post to the forum for him. Since he does lots of cross db queries between different versions, disabling SQL Prompt completely is not a good workaround for him.
thanks
Eric / comments
I may have skipped the last beta. From what I remember when I tried it I just added the path of the Compact db in the exclusion tab.
After I installed the release on a developer's desktop working w...
Ignore server & db problem in released version
This worked with a pre-release version but enhancements in the RTM are causing some problem with SSMS.
When working with SQL Server 2005 Compact, the Ignore Server/db settings don't work anymore. T...
Unhelpful messages
Hi,
The Message report can have hundreds (I have 583 in one project) messages and some of them are useful but very hard to find because they are hidden among "normal" ones.
Ex:
Unable to resolve ob...
Problem with Synonyms
This can be seem as a problem or a feature request for version 3.x or version 4.0:
Synonyms do not seem to be supported. They do not show up in the list of tables (arguably, it could be in a separa...
Hi Bart,
Ignoring the db works. Good enough workaround. Thanks!
Eric
Happy New Year!!
[/img] / comments
Hi Bart,
Ignoring the db works. Good enough workaround. Thanks!
Eric
Happy New Year!!
[/img]
Swallowing would be a good first step but it will still freeze the UI at least 10 sec. each time. Would there be a way to flag a registered server so SQL Prompt ignores it?
Or, since those db are shown as [C:\...] in SSMS, a SQL Prompt option could be to ignore dbs with paths in their names. Quite crude, but efficient workaround if the elegant solution is expensive in time for the v3 release.
thanks,
Eric / comments
Swallowing would be a good first step but it will still freeze the UI at least 10 sec. each time. Would there be a way to flag a registered server so SQL Prompt ignores it?
Or, since those db are s...
Thanks for replying so quickly.
A workaround I am using is to deactivate SQL Prompt when working in split view (I absolutely need split view sometimes). This brought a simple thought: the enable/disable could possibly be available in the toolbar which is easier to access than the menu (if you have access to adding your stuff in the toolbar of SSMS).
BTW, possibly because I haven't become familiar enough, I always prompt SQL Prompt manually with Ctr-space. The default Enter configuration was driving me mad because it was inserting stuff all the time when I was simply trying to format my code. Using Ctr-Space does not bother me but I am curious of the default behavior: what am I missing? How can we use Enter normally (I tried shift-enter and other variations but the auto-complete was always triggered)?
Thanks,
Eric / comments
Thanks for replying so quickly.
A workaround I am using is to deactivate SQL Prompt when working in split view (I absolutely need split view sometimes). This brought a simple thought: the enable/di...
Bug in split view
Not a showstopper, just irritating:
1. with a long script or sp, split the window and position each pane to different part of the script
2. try typing in one pane and as soon as sql prompt auto-com...
Crash in SSMS because it tries to connect to SQL 2k5 Compact
When using SSMS with a SQL Compact database, SQL Prompt crashes because it tries to connect to the db. (error stack below)
I would suggest just to skip SQL Compact support and not trying to connect...
I could, but it seems that applying several patches (VSTS SP1 among them) fixed the problem.
BTW, improvements are impressive! We had a buch of V1 licenses, then moved to the free but quite buggy V2 but did not participate in the V3 beta because of time constraints.
Can't wait to order a few :P
Never thought it would/could be improved that much...
Eric / comments
I could, but it seems that applying several patches (VSTS SP1 among them) fixed the problem.
BTW, improvements are impressive! We had a buch of V1 licenses, then moved to the free but quite buggy V...