After comparing, merging, changing, updating model, all FK are duplicated.
Windows 7
Toad Data Modeler
After comparing, merging, changing, updating model, all FK are duplicated.
Windows 7
Toad Data Modeler
Hello there,
Could you please give us some more information?
Regards,
Lukas
Hi, follow the requested information:
The DDL script is generated with double index references:
**CREATE INDEX [IX_Relationship40] ON [dbo].[PROPOSAL] ([ID_CHANNEL],[ID_CHANNEL])
ON [PRIMARY]
go
CREATE INDEX [IX_Relationship41] ON [dbo].[PROPOSAL] ([ID_OPERATION],[ID_OPERATION])
ON [PRIMARY]
go
CREATE INDEX [IX_Relationship42] ON [dbo].[PROPOSAL] ([ID_PROPOSAL_SCORE_RESULT],[ID_PROPOSAL_SCORE_RESULT])
ON [PRIMARY]
go**
Statistic:
RE Microsoft SQL Server 2008 RE Microsoft SQL Server 2008 + - <> = Commit
Attribute: 447 447 0 0 3 444 3
Entity: 41 41 0 0 8 33 8
Filegroup: 1 1 0 0 0 1 0
Foreign Key: 46 46 0 0 0 46 0
Function: 1 1 0 0 0 1 0
Index: 46 46 0 0 13 33 13
Index Item: 46 46 0 0 0 46 0
Key: 41 41 0 0 5 36 5
Key Item: 41 41 0 0 0 41 0
Procedure: 47 47 0 0 16 31 16
Relation: 46 46 0 0 0 46 0
Schema: 13 13 0 0 0 13 0
User: 4 4 0 0 0 4 0
User Group: 10 10 0 0 0 10 0
Regards
From: bounce-LukasKnapek@toadworld.com
To: tdm@toadworld.com
Subject: RE: [Toad Data Modeler - Discussion Forum] Problem on any compare process using TDM with SQL Server 2008
Date: Mon, 6 Apr 2015 23:55:48 -0700
RE: Problem on any compare process using TDM with SQL Server 2008
Reply by Lukas Knapek
Hello there,
Could you please give us some more information?
Regards,
Lukas
To reply, please reply-all to this email.
Stop receiving emails on this subject.
Or Unsubscribe from Toad Data Modeler - General notifications altogether.
Toad Data Modeler - Discussion Forum
Flag this post as spam/abuse.
Hello again,
We’ve reproduced the issue, it is a bug that affects your beta version - 5.4.5.3. If you have a model with a non-identifying relationship and a child entity with a FK index, the index attribute(s) will be duplicated after Model Update, even when no differences are found.
The issue has been already fixed in the upcoming TDM 5.4 full version so you can either wait until its release, or try doing the same action in TDM 5.3, where the issue doesn’t seem to be present.
Thank you for your report!
Regards,
Lukas