Comments
Sort by recent activity
Hi, it's a fairly simple process to do what you need to do. After you choose your source, let's say production in this case, and the target, dev in this case, you click compare. You'll get something like this: [image] [image] On the left, there's the + sign. Expand that: [image] [image] From there you can tick the check boxes of the tables you don't want to overwrite. [image] [image] Then you can click deploy [image] [image] That's it! You can use Data Compare to deploy or create a script for deployment, whichever you prefer. You can also choose to back up the target db, just in case anything goes wrong. / comments
Hi, it's a fairly simple process to do what you need to do. After you choose your source, let's say production in this case, and the target, dev in this case, you click compare. You'll get somethin...
Try updating to version 10.14.23 (the latest) and see if that corrects the issue. / comments
Try updating to version 10.14.23 (the latest) and see if that corrects the issue.
Hello, That seems strange that it wouldn't be found. Which version of SSMS and SQL Prompt are you using? / comments
Hello, That seems strange that it wouldn't be found. Which version of SSMS and SQL Prompt are you using?
Redgate doesn't support partitioning the tables. If you'd like to do that, you could back up your repository and give it a try. / comments
Redgate doesn't support partitioning the tables. If you'd like to do that, you could back up your repository and give it a try.
Do you need to maintain a large amount of historical data in your data repository? If not, you can try changing your retention settings to a different length of time to reduce the amount. You can also check to see that Data Compression is enabled. / comments
Do you need to maintain a large amount of historical data in your data repository? If not, you can try changing your retention settings to a different length of time to reduce the amount. You can a...
Hello, I've looked through documentation as well and it does appear that this needs to be a custom metric. I didn't find anything that would designate specific backup types as the only valid source. / comments
Hello, I've looked through documentation as well and it does appear that this needs to be a custom metric. I didn't find anything that would designate specific backup types as the only valid source.
Have you had this issue occur again recently? I think we may need to move this to a ticket as we'll need to look at logs and possibly set up a call. / comments
Have you had this issue occur again recently? I think we may need to move this to a ticket as we'll need to look at logs and possibly set up a call.
Hello, It doesn't appear to be related to alert suppression, since you receive the alert outside the suppression window at 8:06am. Does it happen on one particular instance or does it randomly occur across several? Does it indicate what time the alert condition happened? Can you provide a screenshot or other details to investigate further? / comments
Hello, It doesn't appear to be related to alert suppression, since you receive the alert outside the suppression window at 8:06am. Does it happen on one particular instance or does it randomly occu...
Hello, Have you taken a look at our documentation for SQL Scripts Manager? You can find that here: https://documentation.red-gate.com/ssm. This might help you determine what you need to do to restore those logs. / comments
Hello, Have you taken a look at our documentation for SQL Scripts Manager? You can find that here: https://documentation.red-gate.com/ssm. This might help you determine what you need to do to resto...
Hello, Setting a default value for NOT NULL columns is the simplest way to get around this problem. You could also try to populate the column with a valid value, for example: UPDATE <table> SET <column> = 'value' WHERE <column> IS NULL; Then you could do your comparison and deployment. / comments
Hello, Setting a default value for NOT NULL columns is the simplest way to get around this problem. You could also try to populate the column with a valid value, for example: UPDATE <table>SET <col...