Comments
Sort by recent activity
Thanks for your reply.
It seems that this always happens, as the erase happens after the backup completes, but before the file is copied to the network share.
I have logged this as a bug with SQL Backup (SB-4420)
However, if you upgrade to SQL Backup 6, the network resilience features will make sure that the backup file is still copied to the network share if you encounter any network glitches or short outages. / comments
Thanks for your reply.
It seems that this always happens, as the erase happens after the backup completes, but before the file is copied to the network share.
I have logged this as a bug with SQL B...
Thanks for your post.
This shouldn't be happening unless you're using ERASEFILES_ATSTART.
I haven't got a SQL Backup 5 environment to test just now, but I will set one up and see if I can recreate your issue. / comments
Thanks for your post.
This shouldn't be happening unless you're using ERASEFILES_ATSTART.
I haven't got a SQL Backup 5 environment to test just now, but I will set one up and see if I can recreate ...
Thanks for your enquiry.
I personally haven't seen this happen before, so it's not a common issue with SQL Response.
When SQL Response triggers an alert, the alert will remain until it is manually cleared by the user.
Could it be that the alert was triggered, but it was never cleared? (right-click > Clear alert) / comments
Thanks for your enquiry.
I personally haven't seen this happen before, so it's not a common issue with SQL Response.
When SQL Response triggers an alert, the alert will remain until it is manually ...
I'm very sorry we didn't update you with the bug tracking number for this.
It is something our developenet team are aware of. For your reference the bug tracking code for it is SP-2648.
It has been approved to be fixed in a future version, but at this stage I can't give you a timeframe for when you can expect it. / comments
I'm very sorry we didn't update you with the bug tracking number for this.
It is something our developenet team are aware of. For your reference the bug tracking code for it is SP-2648.
It has been...
I've recreated the issue and I think the problem is down to a minor bug we have.
The bug is that <include>Identical</include> is case sensitive. Identical needs to have a capital 'I'.
We have a patch that resolves this issue, or you could simply amend your arg file to include the case sensitive value.
If you would like to try the patch version, you can download it from http://www.red-gate.com/messageboard/viewtopic.php?t=9860
I hope this helps. / comments
I've recreated the issue and I think the problem is down to a minor bug we have.
The bug is that <include>Identical</include> is case sensitive. Identical needs to have a capital 'I'.
We have a pat...
Thanks for your post.
I think this might be related to command line issue SC-4542 where identical objects are also included in the migration script.
Can you try excluding the identical objects using: <exclude>identical</exclude>
Let me know how this goes. / comments
Thanks for your post.
I think this might be related to command line issue SC-4542 where identical objects are also included in the migration script.
Can you try excluding the identical objects usin...
If that didn't help, then it must be a different issue.
I will try and reproduce the symptoms and let you know if anything can be done. / comments
If that didn't help, then it must be a different issue.
I will try and reproduce the symptoms and let you know if anything can be done.
Thanks for your post.
This error nomally indicates that you have a corrupt object somehwre in your schema. Often it turns out that the object has somehow ended up without an owner.
If you would like us to try and figure out which exact object cause the error, then please feel free to send us SQL Comapre snapshots of the source and target schema to support@red-gate.com. You can create snapshots using File > create snapshot in the SQL Compare UI.
If you are an SDK user, you could try to debug the comparison in visual studio to find the object that caused the failure.
I hope this is helpful. / comments
Thanks for your post.
This error nomally indicates that you have a corrupt object somehwre in your schema. Often it turns out that the object has somehow ended up without an owner.
If you would lik...
Thanks for your post.
Unfortunately, this is a known issue when using SQL Prompt 4.0 with large scripts.
We have a bug open for this, and should hopefully make some improvements in the next version.
For your reference the bug tracking code for this is SP-2809.
Sorry for the inconvenience. / comments
Thanks for your post.
Unfortunately, this is a known issue when using SQL Prompt 4.0 with large scripts.
We have a bug open for this, and should hopefully make some improvements in the next version...
Thanks for your post.
This isn't configurable through SQL Comapre, so I think the only workaround would be to use a find and replace function of a text editor.
Can I ask why you want to do this? Is it so you can run the script though another application? / comments
Thanks for your post.
This isn't configurable through SQL Comapre, so I think the only workaround would be to use a find and replace function of a text editor.
Can I ask why you want to do this? Is...