Comments
3 comments
-
Hi,
Thanks for posting. We are aiming to make SQL Prompt 3 much more like VS intellisense, which will hopefully solve your problem with the '=' sign. Sorry about your other problem. Could you tell me a bit more about your system? OS, language settings, SQL Server versions, editor, machine specs?
Regards,
Tilman -
My development machine is a IBM T42 laptop (windows XP 768MB of Ram and 1.69GHZ Processor) I always have trouble when I connect to our productions database not the ones my local machine (My local databases are just a small portion of the production ones so not nearly as many tables) . There are a few different servers which I connect to and I'm not sure of the exact specs, but they are all SQL Server 2000 with all of the service pack/patches installed and lots of RAM and 2 or 4 processors. As for the language every thing on my computer is English and I do all of my SQL programming in Query Analyzer. The version of my local SQL server is 8.00.2039.
-
I don't how many other people use it with VS.NET but it is really fustrating that they work in dffirent way in terms of key and completion. It would be great if they worked in the same way as VS.NET. For example CTrl + Space activated the surgestion.
Add comment
Please sign in to leave a comment.
The other problem I have is most likely a bug. It works fine on a lot of databases I use, but we have some database with 2,000+ tables and 4000+ SP and some of those tables may have 300 or more fields in them. SQL prompt will start off working when I need to bring up my first suggestion, but normally after the first or second time it just won’t work any more. I have also noticed that several times that when it quits working that it will tie up 100% of my CPU usage until I go to task manager and do an end task on it.