Comments
Sort by recent activity
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.
Thanks, Aaron. I was kind of expecting it to be an option because of something like this. I appreciate having the choice. [image] / comments
Thanks, Aaron. I was kind of expecting it to be an option because of something like this. I appreciate having the choice.
Thanks, Aaron. Downloading the updated beta now. / comments
Thanks, Aaron. Downloading the updated beta now.
I'm pretty sure that the SQLCMD options referenced in that article have to do with OUTPUT not INPUT. Reading through the thread and looking at the options, it doesn't seem like they'd apply.
As for the file length, SQLCMD keeps going through the file after the failures. It just doesn't have a variable @pv to process the BLOB data in those particular batches.
Today I plan to try the scripts again without the option to break the transactions apart. Hopefully that will help. However, there still seems to be something off when choosing to split the script into multiple batches and declaring the @pv variable correctly. I'm pretty sure this worked in an earlier release, but don't recall which and I tweaked my scripts since then to disable triggers as well as PK/FK constraints when generating them. / comments
I'm pretty sure that the SQLCMD options referenced in that article have to do with OUTPUT not INPUT. Reading through the thread and looking at the options, it doesn't seem like they'd apply.
As for...
Tried the option to generate a script as one single script, no transactions. I still got the error with @pv not being declared properly.
I really think there is an issue with Data Compare not declaring the @pv variable in the correct place if the options are chosen to disable FK constraints and triggers. / comments
Tried the option to generate a script as one single script, no transactions. I still got the error with @pv not being declared properly.
I really think there is an issue with Data Compare not decla...
Brian Donahue wrote:
My thought is, that if it works in SQL Data Compare but not from sqlcmd, perhaps there is some option you can change in sqlcmd? I'm not sure how sqlcmd deals with batches and transactions.
I'll regenerate the scripts soon, but SQLCMD should work as a standard SQL Script. I can't declare a variable in one batch and then use it in a different batch. If Data Compare is not appropriately declaring the variables within their batches, that's a problem that should be addressed. / comments
Brian Donahue wrote:
My thought is, that if it works in SQL Data Compare but not from sqlcmd, perhaps there is some option you can change in sqlcmd? I'm not sure how sqlcmd deals with batches an...