Comments
Sort by recent activity
I purchased v1.4 for $25 US in November 2005. Working for a small non-profit Company, we watch every penny ('cos there aren't many to go around). When the price was $25 for a fairly well supported ADD-IN, it was a good deal - bugs included because productivity increase outweighed the bug impact.
I understand that Red-Gate needs to:
1. Recoup the product purchase outlay.
2. Cover bug-fixing efforts.
3. Cover the "enhancements" efforts - as we don't know what the "Enhancements" are it's somewhat difficult to judge how much that really amounts to.
4. Cover marketing costs etc. and put some money in the kitty for support costs.
Does all this justify a hike of $70 a copy?
Does $95 for a VS/QA etc ADD-IN sound reasonable? Given that "bulk pricing" may bring the per-copy outlay down, it's still a steep price for an ADD-IN.
Maybe someone needs to reconsider the $$$ aspect... / comments
I purchased v1.4 for $25 US in November 2005. Working for a small non-profit Company, we watch every penny ('cos there aren't many to go around). When the price was $25 for a fairly well supporte...
Would Red-Gate please post a list of bug fixes for those of us who are versant with the "idiosyncrasies" of the v1.4 add-in?
That way, we won't litter the forum with unnecessary posts... [image]
Richard's post highlights a problem that I hope is fixed in v2.0. The CPU gorging can go on for minutes at a time, rendering the workstation nigh on useless during that time. Even Task Manager struggles to come up because PromptSQL is eating so many cycles. / comments
Would Red-Gate please post a list of bug fixes for those of us who are versant with the "idiosyncrasies" of the v1.4 add-in?
That way, we won't litter the forum with unnecessary posts...
Richard's...
If you code your SELECT then, on a newline, code your FROM clause, with table aliases, you can readily return to the SELECT and PromptSQL will show you the columns when you type the table alias.
You get used to it quite quickly... / comments
If you code your SELECT then, on a newline, code your FROM clause, with table aliases, you can readily return to the SELECT and PromptSQL will show you the columns when you type the table alias.
Yo...
Bernards, "put columns at the top of the list and functions last" really gets my vote. v1.4 is a good tool, but it is frustrating to have to turn off useful options in order to see the columns... / comments
Bernards, "put columns at the top of the list and functions last" really gets my vote. v1.4 is a good tool, but it is frustrating to have to turn off useful options in order to see the columns...
As I'm constantly using the 1.4 version, and with the demise of the snippets Import, I've had to uninstall v2.0 and reinstall v1.4.
Coexistence would have been a better approach, especially as you could have gone for the replacement option with a 'live' product - who cares what you do with beta? It's by definition "disposable".
We CAN turn the original OFF - right-clicking the tray icon and "EXIT". Where's the co-existence problem then?
Would have liked to put v2 through its paces... Guess I'll have to wait for my freebie [image] / comments
As I'm constantly using the 1.4 version, and with the demise of the snippets Import, I've had to uninstall v2.0 and reinstall v1.4.
Coexistence would have been a better approach, especially as you ...
If I'm typing one of the "capitalize" words and I happen to be in a literal, the tool SHOULD NOT capitalize. It does in v1.4.
As I've reverted to 1.4 for daily use, I can't actually verify this behavior is fixed without some down time - can't afford it, sorry [image]
Is this bug fixed? / comments
If I'm typing one of the "capitalize" words and I happen to be in a literal, the tool SHOULD NOT capitalize. It does in v1.4.
As I've reverted to 1.4 for daily use, I can't actually verify this be...
All the behaviors you mention, especially the "where's my cursor gone???" were in the original product.
Have you noticed how Query Analyzer suddenly goes on a "go slow" for no good reason? Tabbing from a newline in the middle of a chunk of existing code seems to provoke this more often than not. Each tab takes a second to "get back to you" - not a productivity aid [image] / comments
All the behaviors you mention, especially the "where's my cursor gone???" were in the original product.
Have you noticed how Query Analyzer suddenly goes on a "go slow" for no good reason? Tabbing...
Please clarify the position with regard to prior owners of Atadore's PromptSQL, as cited in the previous post. Hopefully you'll still charge around $20 a copy [image] / comments
Please clarify the position with regard to prior owners of Atadore's PromptSQL, as cited in the previous post.Hopefully you'll still charge around $20 a copy
Not the most intuitively obvious - guess I should read the "What's New" :oops: / comments
Not the most intuitively obvious - guess I should read the "What's New" :oops:
Red Gate Support commented, "...the UI uses an internal SQL compact database to cache the history. It is the syncing process between the system tables and the cached database where the performance issue is seen. We do have an existing request logged to improve the UI performance in these types of situations. The number for your reference is SB-4400. I will add you to the list of requestors. In the meantime, the workaround that has worked for other customers is to reduce the number of rows in the table. Sorry for the inconvenience."
I dropped the SQL Backup history to 10 days and left the UI open - the message on the Server Options dialog says that cleanup only takes place when the UI is open. I see that as a DEFECT because I only ever go to the UI when adding or updating a scheduled backup, or to get the full log message for a rare failure. Cleanup should be something SQL Backup takes care of on its own - the essence of an unattended process - especially because the service knows to write to the history, so it surely can do cleanup, too.....
At least I received a response in about 45 seconds. Much better, but still very slow... SELECT TOP(N) FROM, perhaps, with paging...?
Pity there's no "Export History" right-click option, either, so at least I could do some average run time, file size, time-of-day impact analysis on a set of data I can see in the UI, rather than run (and generate an "Unable to generate report" error via the UI "Query error: There was an error parsing the query. [Token line number=1, Token line offset=2, Token in error]" Not exactly helpful with no means of copying that error to the clipboard...) Ah well... / comments
Red Gate Support commented, "...the UI uses an internal SQL compact database to cache the history. It is the syncing process between the system tables and the cached database where the performance ...