Activity overview
Latest activity by CWuestefeld
Query window in VS.Net
Am I missing something? SQLPrompt is working nicely in VS.Net for editing stored procs. However, it doesn't seem to know that Query windows exist at all. That is, when I open a query window either ...
I think this is annoying as well. I can't imagine why it's the default, as I've never seen brackets used by anyone except non-professionals who didn't know enough not to put spaces in the names.
Anyway, it's easy to turn off. Just bring up the SQL Prompt Options. Go to the 3rd tab, "Style". Under "Formatting" is a checkbox that says "Surround with brackets []". / comments
I think this is annoying as well. I can't imagine why it's the default, as I've never seen brackets used by anyone except non-professionals who didn't know enough not to put spaces in the names.
An...
Bad alias abbreviation
This is odd. Generally the aliasing of tables works fine. But it happens that the very first one I tried is the only one that I can make break consistently:SELECT * FROM Asset w
Where the heck di...
I'm back in business! 8)
Deleting that registry key did the trick. / comments
I'm back in business! 8)
Deleting that registry key did the trick.
Yes, logging on as a different user does work just fine. Unfortunately, I need to be me. / comments
Yes, logging on as a different user does work just fine. Unfortunately, I need to be me.
Sorry, Neil, the proposed fix does not fix the problem. QA still exits immediately when started while SQLPrompt3's integration is enabled. [image] / comments
Sorry, Neil, the proposed fix does not fix the problem. QA still exits immediately when started while SQLPrompt3's integration is enabled.
Lionel wrote:
Another thing that I forgot to ask is what version of Query Analyzer do you have.
It's 8.00.760. / comments
Lionel wrote:
Another thing that I forgot to ask is what version of Query Analyzer do you have.
It's 8.00.760.
I'm running Windows Server 2003 with all the latest patches (but not IE7).
I've got 1GB RAM. My current commit charge is 718MB, currently with a limit of 1,734MB. It's got a 2.8GHz Pentium4 single-core CPU.
This happens even very soon after booting, before too much garbage is running.
I don't think that SQLPrompt is even getting as far as attempting to connect to a database. QA never gets far enough to show a UI, so I don't think it knows where to connect to yet.
This machine did have Beta 1 installed on it. I did uninstall it and there is no trace of the install directory. But maybe something's left in the registry...? / comments
I'm running Windows Server 2003 with all the latest patches (but not IE7).
I've got 1GB RAM. My current commit charge is 718MB, currently with a limit of 1,734MB. It's got a 2.8GHz Pentium4 single-...
Won't work with QA
When I run the new beta with QA, the isqlw process starts and then immediately shuts down. A reboot did not help. If I disable "Start sQLPrompt when you start Query Analyzer", QA is able to run fin...
Beta 1 participants
If you've already purchased SQL Prompt 3 will be able to activate this version of the product with the license key(s) you’ve been sent.
Does this mean that those of us who participated in Bet...