Comments
6 comments
-
Hi @tdennis2019
Thanks for reaching out to us regarding this. My apology for the delay in coming back to you!
In all honesty, I have never used SQL Graph tables before now. To aid my attempts to reproduce the behavior you are seeing here, are you able to provide an example Graph table I can use for this?
Also, just for absolute clarity, was the graph table(s) in question created in SQL 2017? Do you see the same behavior in SQL Graph tables created in SQL 2019?
-
They were created in SQL 2019 Developer edition. I can reproduce it using the sample tables from this website: Introduction to SQL Server Graph Tables (iterationinsights.com)
-
They were created in SQL 2019 Developer edition. I can reproduce it using the sample tables from this website: Introduction to SQL Server Graph Tables (iterationinsights.com)
-
Hi @tdennis2019
My apology for the delay in coming back to you on this.
I just wanted to clarify if the fix released as part of SQL Compare v.14.8.4 (https://download.red-gate.com/checkforupdates/SQLDataCompare/SQLDataCompare_14.8.4.21440.exe) has also resolved the issues you have highlighted here? -
Hi Dan,
I get a 404 file not found error when I click the link you provided.
-
Hi @tdennis2019
Apologies - looks like there is a ) at the end of the link
Please try the following:
https://download.red-gate.com/checkforupdates/SQLDataCompare/SQLDataCompare_14.8.4.21440.exe
Add comment
Please sign in to leave a comment.
1. The hidden node columns are not automapped.
1a. If the node columns are mapped manually, the table does not appear in the data comparison results. Going back into Edit Project removes the manual mapping
2. Selecting Deploy without the hidden node columns means new $node_id values are generated which then breaks referential integrity with all the Edge tables linked to the Nodes.
Will SQL Data Compare be updated soon to handle the Node and Edge tables?
Thank you