Comments
Sort by recent activity
I will need to see if I can re-create the problem. It happened after I used SSMS against a SQL 2000 SP4 server to Modify a proc, then copied part of that proc, selected everything, and pasted my section over the whole (I just needed to use that section of code for some custom work). After that, every time I aliased something it would prompt for a connection the first time I tried to use it and afterwards it would work as expected. If I can reproduce it I will definitely send it back.
The aliases were pretty short - a, ad, ip, ss - none of these overlapped an existing DB or linked server.
I'm logged in as a SQL Login, member of SysAdmin, but not "sa".
We have ~10-15 DB's on the server.
-Pete / comments
I will need to see if I can re-create the problem. It happened after I used SSMS against a SQL 2000 SP4 server to Modify a proc, then copied part of that proc, selected everything, and pasted my s...
Looks like the 3.5 RC made some significant headway for me. You may want to give it a try.
-Pete / comments
Looks like the 3.5 RC made some significant headway for me. You may want to give it a try.
-Pete
Also - quick note for those mentioning the VM thing. MS offers up Virtual Server (and I think Virtual PC) free of charge. VMWare has a free version of their server product. While neither are extremely full-featured, you can easily download and install them and set up a new OS. You can even do some basic snapshots/differences on your virtual hard drive for an easy restore to state (like before you installed Katmai so you can restore the snapshot and have a clean system without messing around with uninstalls that may or may not work [image] )
-Pete / comments
Also - quick note for those mentioning the VM thing. MS offers up Virtual Server (and I think Virtual PC) free of charge. VMWare has a free version of their server product. While neither are ext...
For those of us who do have VMs into which we've installed Katmai, what are the licensing concerns for SQL Prompt? Can we install into the VM because it's still on our local box? Do we need a new copy? Just install an unregistered version? I'd like to play around with that some, but will not bother if I have to buy a version just to test with and I don't want to ding any sort of activation counts I may have on my account for a test instance either. Testing is nice, but I'll live without it if it affects my account.
Thanks.
-Pete / comments
For those of us who do have VMs into which we've installed Katmai, what are the licensing concerns for SQL Prompt? Can we install into the VM because it's still on our local box? Do we need a new...
Not sure how it works in your mode, but I set up snippets for my use and am able to type the snippet, then hit enter or tab (or sometimes even a period) and it puts in the code. My biggest problem is that it seems to do this too quickly most of the time. e.g. I've aliased one of my tables with an "i", but it's not in the current database. When I later try to type "i." + ColumnName, I often get INFORMATION_SCHEMA() popping up before I can blink. Undo, repeat, undo, repeat again, undo, type really quickly or hit ESC to stop the popup. :P
-Pete / comments
Not sure how it works in your mode, but I set up snippets for my use and am able to type the snippet, then hit enter or tab (or sometimes even a period) and it puts in the code. My biggest problem...
Agreed on the prompt window size. I'm constantly increasing the size of that thing when I work just so I can read the column names and not choose the wrong one time after time.
Can't speak on the double quote issue.
-Pete / comments
Agreed on the prompt window size. I'm constantly increasing the size of that thing when I work just so I can read the column names and not choose the wrong one time after time.
Can't speak on the ...
I guess this would be a good time to put in for another menu item - SQL Prompt On/Off. Sure we can set it in options, but just like the cache refresh, we have to open another window to do that when what we really need is a quick-hit to just toggle something. I realize that we can't necessarily add a button easily to the toolbars to do that or define hotkeys (which may be in use already), but these sorts of items directly on the main SQL Prompt menu would be really helpful. I get hit by doing a REPLACE on a relatively large script (replacing an key value because the script runs piecemeal and I need to replace that value everywhere it appears). Have to wait 30+seconds to do the update regularly. [image]
-Pete / comments
I guess this would be a good time to put in for another menu item - SQL Prompt On/Off. Sure we can set it in options, but just like the cache refresh, we have to open another window to do that whe...
For the cross-database coding, you'll have to check out some of the other threads. My main problem with it right now (other than not working) is that I'll alias a table - e.g. MyTable as i - and I'll get the intellisense popping up so fast that when I attempt to use "i" later, I get IDENTITY() or whatever the first entry under "i" is for the intellisense helps. Maybe that will change when it works as expected. [image]
Agreed that there isn't that much need for a hotkey for refresh, just not needing to dig down through all of those menus. An extra button or something right on the main menu would be helpful.
-Pete / comments
For the cross-database coding, you'll have to check out some of the other threads. My main problem with it right now (other than not working) is that I'll alias a table - e.g. MyTable as i - and I...
Agreed on the size of the drop-down box. I also have large field names and have a lot of trouble determining which is which.
Also like the idea of a refresh button or hot-key for the current database instead of digging through menus and all that. While that works, it's not really user-friendly when you just want to update a single DB's schema.
-Pete / comments
Agreed on the size of the drop-down box. I also have large field names and have a lot of trouble determining which is which.
Also like the idea of a refresh button or hot-key for the current datab...
Thanks for the update, Bart. This is a minor issue for me, though I do notice that the larger the script, the slower the IDE is when I make a global change/replace (e.g. a large script to scrub data where I change a Customer ID globally each time I run it - a sadly manual process due to the potential to cause great damage)
I have to admit that I'm looking forward to the next release. Heck, I'd almost be willing to manually install the beta rather than mess with an installer. [image]
-Pete / comments
Thanks for the update, Bart. This is a minor issue for me, though I do notice that the larger the script, the slower the IDE is when I make a global change/replace (e.g. a large script to scrub da...