Comments
Sort by recent activity
Thanks for contacting us and I apologize for the late reply,
I think that using the RESEED option in Data Compare may fill in the deleted IDs causing this issue.
If you disable that option - it will not Reseed when inserting/updating/deleting records.
Warm Regards, / comments
Thanks for contacting us and I apologize for the late reply,
I think that using the RESEED option in Data Compare may fill in the deleted IDs causing this issue.
If you disable that option - it wil...
Hey Brian,
Thanks for posting!
That is not currently an option (mainly because it does the comparison based on the identity values), but that does does sound like something we could add in the future. I recommend you post your idea in our UserVoice forum here
Do let me know if you have any other questions or issues!
Warmly, / comments
Hey Brian,
Thanks for posting!
That is not currently an option (mainly because it does the comparison based on the identity values), but that does does sound like something we could add in the futu...
Hey mmelvin,
Thanks for contacting us!
It does not support SSMS 2005 and older - what version(s) of SSMS are you on currently?
Do you have SQL Source Control installed already?
Warm Regards, / comments
Hey mmelvin,
Thanks for contacting us!
It does not support SSMS 2005 and older - what version(s) of SSMS are you on currently?
Do you have SQL Source Control installed already?
Warm Regards,
We solved Noel's issue by creating the Filter using SQL Compare (to confirm exactly what it included/excluded). We also discussed the IncludeDependencies option that is on by default (and it may be the source of his issue), but it can be disabled by putting a minus sign in front of the option like -IncludeDependencies,OtherOption The includeAdditional option works similarly to how in Compare it suggests that you deploy dependencies along with the objects that you are deploying, so you can do some tests with that to make sure that the filters and options are working the way you intend. / comments
We solved Noel's issue by creating the Filter using SQL Compare (to confirm exactly what it included/excluded).We also discussed the IncludeDependencies option that is on by default (and it may be ...
Hey Ramunas,
Thanks for posting!
Off the top of my head, I'm not sure why it would do that.
If you are still experiencing this - could you send in an email to Support@red-gate.com along with the full deployment log, the Release package (which contains the Changes.html file as well as the Source and Target scripts folders) that is created by the Create Database Release step, and a screenshot of your Create Database Release step definition.
Kind Regards, / comments
Hey Ramunas,
Thanks for posting!
Off the top of my head, I'm not sure why it would do that.
If you are still experiencing this - could you send in an email to Support@red-gate.com along with the fu...
Thanks for the vigorous discussion!
I am a Technical Support Engineer over at Redgate, so I should be able to help. @chris_godfree The Source Control Options are not passed to DLM Automation, but Filters are not Options - Filters are passed from SQL Source Control and should be used throughout the pipeline. @noelc As I mentioned before - the only thing that would override the Filter file is the IncludeDependencies option which is enabled by default (see my previous post) - unless this was a bug with the version of DLM Automation you are using.
So I would need a copy of your Release package (a package created by the "Create Database Release" step) to fully understand what occurred.
We have a ticket open as well - so you would be able to send in the Release package there.
Kind Regards, / comments
Thanks for the vigorous discussion!
I am a Technical Support Engineer over at Redgate, so I should be able to help.@chris_godfree The Source Control Options are not passed to DLM Automation, but F...
Thanks for contacting us!
By default, DLM Automation has the IncludeDependencies option enabled. So it will deploy those dependencies even if they are Filtered out. https://documentation.red-gate.com/display/DLMA2/Using+SQL+Compare+options+with+Addons
I would need your full build log as well as the build package to confirm that - but it seems like the most likely answer.
You can disable it by putting a minus sign in front of "IncludeDependencies" and putting that in the Compare Options field.[image]
Static Data is best understood in the context of SQL Source Control and it can be stored in the Build package and deployed along with the schema scripts. If there are no data scripts in the package then no data will be deployed.
I've also followed up via email for further troubleshooting.
Warm Regards, / comments
Thanks for contacting us!
By default, DLM Automation has the IncludeDependencies option enabled. So it will deploy those dependencies even if they are Filtered out. https://documentation.red-gate.c...
Hey Kshin,
Thanks for contacting us and sorry you are having this issue!
I've followed up via email for more info on this.
We have made many improvements to how the tool handles temporal tables, but we are always interested in addressing gaps in compatibility.
Warm Regards, / comments
Hey Kshin,
Thanks for contacting us and sorry you are having this issue!
I've followed up via email for more info on this.
We have made many improvements to how the tool handles temporal tables, bu...
Hey SteveNOV,
Thanks for contacting us!
We don't currently deploy server/database properties (like the collation) along with the database objects - however, the tool OmniCompare can do that comparison and deployment for a variety of different Server and Database level properties - http://aireforge.com/
Also, I recommend you post this idea to our UserVoice forum available here
Do let me know if you have any questions or issues with that!
Warmly, / comments
Hey SteveNOV,
Thanks for contacting us!
We don't currently deploy server/database properties (like the collation) along with the database objects - however, the tool OmniCompare can do that compari...
Hey amalik,
Thanks for contacting us!
If they are identical it should output exit code 63 - see documentation on exit codes https://documentation.red-gate.com/display/SDC12/Exit+codes+used+in+the+command+line
If you use the GUI, are the two backups actually identical? / comments
Hey amalik,
Thanks for contacting us!
If they are identical it should output exit code 63 - see documentation on exit codes https://documentation.red-gate.com/display/SDC12/Exit+codes+used+in+the+c...