Comments
Sort by recent activity
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...
Just wanted to add in the doing a Find/Replace also seems to take much longer than with SQL Prompt 2. I don't notice it for really short scripts, but I've got a couple of scripts in the 1000's of lines and those definitely take a while where they used to happen almost instantaneously.
-Pete / comments
Just wanted to add in the doing a Find/Replace also seems to take much longer than with SQL Prompt 2. I don't notice it for really short scripts, but I've got a couple of scripts in the 1000's of ...
While I'm thinking about this, I think that it's also affecting just selecting text. If I hold down shift and arrow up or down, SSMS takes quite a while to highlight the rows and the only indicator I have that I'm selecting is a small blue line on the left side of the row. If I'm de-selecting, I have nothing.
Running the SP2 CTP on my local box if that helps to test.
-Pete / comments
While I'm thinking about this, I think that it's also affecting just selecting text. If I hold down shift and arrow up or down, SSMS takes quite a while to highlight the rows and the only indicato...
I was a PromptSQL customer as well and I have mixed feelings about the Red-Gate upgrades. I used SQL Prompt 2 in between versions and it had lost some of the functionality of PromptSQL while fixing some of the bugs. SQL Prompt 3 has lost a little of the functionality of SQL Prompt 2 (while admittedly adding other functionality).
There are times I've been tempted to load up that old version of PromptSQL with all of the little bugs just because it did some things better. Other times, I remember some of the more annoying bugs and will just stick with what I have. I am considering rolling back to SQL Prompt 2 until the next dot release of 3 because of the missing cross-database support. I do a lot of those queries and now do a lot of typing.
Also, while I don't have a major issue with being charged for upgrades, the price difference between PromptSQL and SQL Prompt 3 is pretty big. I paid for PromptSQL out of my pocket - didn't even hesitate after using it for about one hour. If I were evaulating SQL Prompt 3 and paying out of my own pocket, it would just be uninstalled. It's useful, but not $200 worth of useful at this point.
I see a lot of potential for the product line and appreciate the developers' work, but I think the product is priced a little too high for what it offers. Besides, I think if it were in the $50 range, it would probably sell more copies just because the average DBA could justify an out-of-pocket expense of that type. Having to go through corporate purchasing for tools can be a royal pain at times and justifying this to most of my bosses would be kind of hard.
Anyway, my $.015 on the matter.
-Pete / comments
I was a PromptSQL customer as well and I have mixed feelings about the Red-Gate upgrades. I used SQL Prompt 2 in between versions and it had lost some of the functionality of PromptSQL while fixin...
I realize that, but it was definitely more convenient when I'm already using the arrow keys to keep on using them. More a matter of efficiency in this case to just keep on using the same keys.
Ideally - give an option to move all of the tablename.column entries to the bottom and still sort the column list per prefs, especially when only working with one table.
-Pete / comments
I realize that, but it was definitely more convenient when I'm already using the arrow keys to keep on using them. More a matter of efficiency in this case to just keep on using the same keys.
Ide...
When should we have received this e-mail? I don't remember seeing one and definitely purchased this software.
Thanks. / comments
When should we have received this e-mail? I don't remember seeing one and definitely purchased this software.
Thanks.