How can we help you today? How can we help you today?

SQL Prompt x.x Stops Working...

Hi,

I use SQLPrompt in SSMS, and find that it's usually good for the first few intellisense lookups, after which anything I do to try to invoke the intellisense popup fails.

Anyone else getting this annoying problem?

SQLPrompt, on the face of it, looks like an excellent utility, however, getting it to work has always been a massive draw-back for me - would love to know where I'm going wrong. Perhaps my 'style' of SQL doesn't agree with SQLPrompts?

Thanks,

Will A.
Hippunky
0

Comments

3 comments

Sort by
  • asentell
    I am experiencing the same thing. It's a great idea, but I need it to work every time I want to use it and to not stop working in the middle of typing.
    asentell
    0
  • void
    Same here. Also, it does not seem to consider queries referring the same table twice, since it seems to skip the JOIN's conditions already used (even though is the same table).

    On the other hand, the PC I use on my work is a bit limited, it only has 256 MB RAM (and I'm not sure if the video card takes some), so I'm not sure if that could be part of the problem --the SQL server I connect to is outside of my own PC, but that shall not be a problem.
    void
    0
  • dm
    A common reason for it to appear to stop working is if there are blank lines in the current query.

    SQL Prompt 2.0 only looks at the chunk of text in the editor around the cursor that is delimited by blank lines ...
    dm
    0

Add comment

Please sign in to leave a comment.