Accepted

Forward engineering SQL Server tables doesn't consider dependencies between tables

4 years ago • updated by 4 years ago • 5

Scripting out my diagram, the output SQL failed when running in SSMS due to the fact the order of the tables were incorrect based on their primary/foreign key relationships and constraints.

Vote

Answer

Accepted

4 years ago

Hi Martijn,

Agree, app doesn't order tables with circular references now.

Thank you for bug report.

Replies 5
Oldest first
- Newest first
- Oldest first

Under review

4 years ago

Thank you for feedback, we will review this ticket soon

Thank you for your assistance,

SqlDBM Team

4 years ago

Dear User,

Sorry for the inconvenience.

Can you please provide us some details to investigate it:

- What are the exact steps to reproduce

- Could you provide the generated script

- Any screenshots which you have, if you think, can help us to understand the problem easily

Please provide above details, so we can detect the bug and resolve it soon.

Thanks

Team - SqlDBM

4 years ago

Hi, we also have this problem. When there are (circular) references between tables, they are not created in the right order. Therefore the create database fails. We have to manually alter the create script to make it work in the right order.

4 years ago

Same problem for dropping databases by the way.

Answer

Accepted

4 years ago

Hi Martijn,

Agree, app doesn't order tables with circular references now.

Thank you for bug report.

Customer support service by UserEcho