Comments
Sort by recent activity
Thanks for your post.
Looking at the error message, it seems that this kind of thing is fairly common when connecting to Azure databases, so MS suggest the application needs to have some retry logic. [http://msdn.microsoft.com/en-us/library/ff394106.aspx]
Both SQL Compare and SQL Data Compare contain retry logic, so you shouldn't get this error because of a lack of retry attempts.
I've asked the dev team if they know what else might be up, and they think it could be caused by a firewall not being properly set up. This will cause the retry to give up and let the error through. / comments
Thanks for your post.
Looking at the error message, it seems that this kind of thing is fairly common when connecting to Azure databases, so MS suggest the application needs to have some retry logi...
And here is said patch: ftp://support.red-gate.com/patches/SQL_ ... .0.181.zip
Let us know how you get on with it. / comments
And here is said patch:ftp://support.red-gate.com/patches/SQL_ ... .0.181.zip
Let us know how you get on with it.
Sorry for the delay, I missed your last update. Thankfully you were just letting me know you solved the problem and didn't have any other questions.
That's interesting that powershell will ignore the other options if they're not wrapped in quotes. I'll have to remember that.
Thanks for letting us know how you fixed it. / comments
Sorry for the delay, I missed your last update. Thankfully you were just letting me know you solved the problem and didn't have any other questions.
That's interesting that powershell will ignore t...
Thanks for your post.
I've tested this with the same version, and the option appears to be working as expected. I tried seeing if the problem might be to do with /include switch or the /excludecolumns switch, but it seemed to still work for me.
Have you tried running the command directly from a command prompt and see if that makes any difference.
Would you be able to post the DDL for the table and I'll try it with the rows of data you posted. / comments
Thanks for your post.
I've tested this with the same version, and the option appears to be working as expected. I tried seeing if the problem might be to do with /include switch or the /excludecolu...
Thanks for letting us know you found the problem.
I believe I was in correspondence with your colleague about this. I assumed it would be bad data, but I can see how this could be caused when you change the data type. / comments
Thanks for letting us know you found the problem.
I believe I was in correspondence with your colleague about this. I assumed it would be bad data, but I can see how this could be caused when you c...
Thanks for your post.
When you're overwriting a database, backing up the tail of the log prevents you from losing any work that was entered to the database since the full backup you're restoring. I suspect the reason certain records didn't go into the first full backup was because they weren't yet committed to the source database at the time you took the first backup. Taking a t-log backup prior to the full backup doesn't force anything to be committed, so I'm not sure this was the reason the records were present in the second full backup. The full backup will contain all committed data that was present at the time you started the full backup.
Anyway, thanks for letting us know you've solved your issue. / comments
Thanks for your post.
When you're overwriting a database, backing up the tail of the log prevents you from losing any work that was entered to the database since the full backup you're restoring. I...
I'm not exactly sure why you would get an error on a CS database, as it should be fine to add another column with only a case difference to the same table.
Could the source db be CS and the target CI? This still wouldn't explain why it's trying to create a new column before it drops the old column.
I'm going to follow this up with a support ticket and see if we can get to the bottom of it. / comments
I'm not exactly sure why you would get an error on a CS database, as it should be fine to add another column with only a case difference to the same table.
Could the source db be CS and the target ...
ah yes, that would make sense.
Thanks for letting me know how you solved the problem. / comments
ah yes, that would make sense.
Thanks for letting me know how you solved the problem.
Thanks for your reply.
Try upgrading to 5.2, because that's the version I tested it it without any problems.
Does this happen will all databases you connect to? / comments
Thanks for your reply.
Try upgrading to 5.2, because that's the version I tested it it without any problems.
Does this happen will all databases you connect to?
Thanks for your post.
Can you let me know the exact SQL Prompt version you're using? I don't get the same problem with my SQL 2000 instance.
Do you get teh same problem if you use a sysadmin account? / comments
Thanks for your post.
Can you let me know the exact SQL Prompt version you're using? I don't get the same problem with my SQL 2000 instance.
Do you get teh same problem if you use a sysadmin account?