Comments
14 comments
-
I've found this annoying too. I get the expiry exception happening everytime i open a new window, even though i have set it to "off". -
Same here !!
I had one Query Analyzer window open from last week and I was getting intellisense, I had opened another connected to different server database and it wasn't working. After invoking Query analyser via Enterprise Manager I finally got the exception about the expiry.
It would have been good to know via a warning a couple of days ago or a post here that it was going to expire or what the plans (if any) were going to be thereafter.
emails4me -
emails4me wrote:It would have been good to know via a warning a couple of days ago or a post here that it was going to expire or what the plans (if any) were going to be thereafter.
It was mentioned in the release notes.
Read the time limitation section.Time Limitation SQL Prompt 3 Beta will stop working on September 17th 2006.
-
Yep OK, I couldn't recall that from last month (I should have set a reminder in outlook) but a message box or a red x over the systray SQL Prompt icon on it wouldn't hurt. It was strange to see it continue to work in one Query Window but not another. I had to coax the exception before I knew that it had expired.
emails4me. -
Hi,
Sorry about the inconsistent and slightly improvised nature of the time bomb. Again it was all down to time constraints.I got the message that SQL Prompt 3.0 Beta is expired.
What to do?
- wait for a new beta (when?)
- get a new license to extend the test
- revert to SQL Prompt 2.0
There probably won't be another beta release. So uninstalling is your only option. Note that the SQL Prompt menu item in SSMS wont be removed automatically. You can do this yourself, however, by right-clicking on the menu bar and dragging the entry off.
Regards,
Tilman -
I've posted a sticky here about SSMS menu items not being removed on uninstall:
http://www.red-gate.com/messageboard/vi ... php?t=3357
It's actually a bug in SSMS itself, however the sticky provides instructions on how to get rid of the menu items.
Thanks,
Bart -
Tilman wrote:There probably won't be another beta release. So uninstalling is your only option.
Will there be some opportunity to try SQL Prompt 3?
Due to reported defects (intellisense that did not repect the context; tab insertion; alias issues) and beta limitations (no SSF snipet) I found SQL Prompt 2 (even with its quirks) helped me get my job done easier. Before I purchase SQLP3 I need to see the defects corrected and the usability improved. -
Hi there,
A release candidate will be available in mid-October. Please refer to http://www.red-gate.com/MessageBoard/vi ... php?t=3358 for more information.
Thanks,
Bart -
I finally got the company to upgrade me from SSMS Express to SSMS, but when I reinstalled SQL Prompt 3, I learned that it had expired
. Is there a reason why the beta cut off so quickly after only two weeks (especially since it was delayed in being released in the first place)?
-
Hi Matthew,
Sorry for the hassle. We often time limit beta releases although the time limit involved does vary. Two weeks is roughly standard on the projects I've worked on. There will be a release candidate available in mid-October so you'll be able to give it a try.
Cheers,
Bart -
It's a shame that both the RedGate beta programs ive participated in so far have always ended up like this
Everyone raises heaps of issues which is obviously good and gives you guys feedback etc as to what users want and testing all th9ose edge cases that you may not be able to replicate... But we never get a second crack at it to let you guys know whether the issues seem to be fixed.
I realise that releasing a beta is a large task... but my suggestion for future is to really look at your beta programs and try and factor in at least 2 beta releases. Im sure alot of people are in the same boat as me in that due to some showstopper/serious type issues already reported, we cant get to certain positions to then test how the tool reacts and let you guys know if this works for us or not. -
rgribble wrote:It's a shame that both the RedGate beta programs ive participated in so far have always ended up like this
Everyone raises heaps of issues which is obviously good and gives you guys feedback etc as to what users want and testing all th9ose edge cases that you may not be able to replicate... But we never get a second crack at it to let you guys know whether the issues seem to be fixed.
I realise that releasing a beta is a large task... but my suggestion for future is to really look at your beta programs and try and factor in at least 2 beta releases. Im sure alot of people are in the same boat as me in that due to some showstopper/serious type issues already reported, we cant get to certain positions to then test how the tool reacts and let you guys know if this works for us or not.
Hi there,
I think this is a fair point, and it's a debate that's just going to run and run here at Red Gate. We've been searching for the ideal solution to the beta question for some time now and clearly this isn't it. For SQL Prompt 3 with the people available unfortunately we just don't have the time to run another beta.
As I said, we will be running a release candidate in mid-October so you can use this to verify that issues have been fixed, and it will initially only be available to beta testers. This also means that if you want to take advantage of the $99 special offer you should be able to make your purchasing decision on the basis of the release candidate (the special offer will expire as soon as the final version is released).
Hope that helps.
Thanks,
Bart -
I'm glad to have had this beta. And although a second beta would be nice, I'm guessing the final version will be great. After all, the other red-gate products I use turned out great even w/o my input. :-)
Unless 3.0 is perfect with no bugs or missing features <chuckle><chuckle>, I hope the 3.x versions keep coming out on a regular basis. -
ROFL. Thanks for your comments. We try not to use patch releases as a crutch, however we pretty much always end up creating a patch release within a couple of months of the original product release so I very much doubt this project will be any different. I think the only exception to this so far has been SQL Log Rescue for which a patch release came out roughly a year after the original version.
Cheers,
Bart
Add comment
Please sign in to leave a comment.
What to do?
- wait for a new beta (when?)
- get a new license to extend the test
- revert to SQL Prompt 2.0
Let me know
Marco