Comments
Sort by recent activity
Hi there,
If you've got an editor open you can just go to SQL Prompt > Enter License Key via the main menu bar. If you're talking about the trial dialog that pops up when you open the editor there should be a button labelled something like "Enter Serial Number", although it's always possible that if you've changed DPI settings this might have migrated off the visible area of the dialog (it shouldn't do, but changing DPI does cause no end of glitches like this). If you still can't find it please let me know.
Thanks,
Bart / comments
Hi there,
If you've got an editor open you can just go to SQL Prompt > Enter License Key via the main menu bar. If you're talking about the trial dialog that pops up when you open the editor there ...
Hi Brian,
There shouldn't be. In fact it should be more stable. Basically the only bug fixes that went in there were for this particular issue, plus a number of exceptions/crashes that have been reported in 3.6 and earlier releases over the past months.
Thanks,
Bart / comments
Hi Brian,
There shouldn't be. In fact it should be more stable. Basically the only bug fixes that went in there were for this particular issue, plus a number of exceptions/crashes that have been re...
Hi Brian,
I'm 99% sure this is fixed in 3.7. The reason I say this is that somebody reported it all of half an hour after we released 3.6 and I was so irritated we'd missed it that I fixed it there and then, but wasn't able to check in the fix for some time. It's certainly not behaving like this in the 4.0 codebase I have on my machine right now, which at present has very few differences from 3.7.
Details at: http://www.red-gate.com/MessageBoard/vi ... 7a86210ebe
Please contact support@red-gate.com directly for download instructions.
The behaviour seems to be that if "Surround identifiers with brackets" is checked then the table name will be surrounded, whereas if it's not checked, then as you'd expect the table name is not surrounded with brackets.
Hope that helps.
Thanks,
Bart / comments
Hi Brian,
I'm 99% sure this is fixed in 3.7. The reason I say this is that somebody reported it all of half an hour after we released 3.6 and I was so irritated we'd missed it that I fixed it there...
OK thanks. That's certainly the problem then. If you have access to it then SQL Server Management Studio doesn't suffer with this problem because it actually gives us full information about undo/redo rather than just saying "hey, something's changed". If you don't have SQL Server 2005 you might find that SQL Server Management Studio Express will happily connect to your SQL Server 2000 instances (I've never tried this though, so no promises). This version of Management Studio is free and can be downloaded from: http://www.microsoft.com/downloads/deta ... laylang=en
It doesn't explicitly say that SQL Server 2000 isn't supported, but that doesn't necessarily mean that it is either. I'm just going by the fact that I use the standard version of SSMS to connect to both 2000 and 2005 instances.
Hope that helps.
Thanks,
Bart / comments
OK thanks. That's certainly the problem then. If you have access to it then SQL Server Management Studio doesn't suffer with this problem because it actually gives us full information about undo/re...
Hi Brian,
That should be fine. I have them both on my machine and haven't had any problems at all.
Cheers,
Bart / comments
Hi Brian,
That should be fine. I have them both on my machine and haven't had any problems at all.
Cheers,
Bart
How big an undo are we talking about here? I only see this kind of behaviour when undoing a massive paste, or similar.
Thanks,
Bart / comments
How big an undo are we talking about here? I only see this kind of behaviour when undoing a massive paste, or similar.
Thanks,
Bart
Hmmm... Which editor is this? I know that we don't/can't always get proper undo/redo events and that this can sometimes force SQL Prompt to reparse a script because we don't know what's changed. AFAIK this only affects QA but I could be wrong about that because I didn't work on the editor integration.
Thanks,
Bart / comments
Hmmm... Which editor is this? I know that we don't/can't always get proper undo/redo events and that this can sometimes force SQL Prompt to reparse a script because we don't know what's changed. AF...
Great stuff! Glad to be able to help.
Cheers,
Bart / comments
Great stuff! Glad to be able to help.
Cheers,
Bart
Hi Brian,
That's not a bug. Please go to SQL Prompt > Options. Then go to Listed Candidates > Performance. Either (recommended) increase "maximum number of recently declared variables to display in the candidate list", or select "Search enter batch/GO block" (recommended only for faster machines, or scripts with plenty of batch markers).
Hope that helps.
Thanks,
Bart / comments
Hi Brian,
That's not a bug. Please go to SQL Prompt > Options. Then go to Listed Candidates > Performance. Either (recommended) increase "maximum number of recently declared variables to display in...
Hi Brian,
Thanks for getting in touch, and apologies for the hassle. I believe this bug has been fixed. Please see this thread for details of a patch that has just been made available: http://www.red-gate.com/messageboard/vi ... php?t=6289
Thanks,
Bart / comments
Hi Brian,
Thanks for getting in touch, and apologies for the hassle. I believe this bug has been fixed. Please see this thread for details of a patch that has just been made available:http://www.re...