Toad World® Forums

BUG: Name Uniqueness problem on automatically generated key

In a SQL Server 2008 model, I keep getting “Name Uniqueness” errors on an automatically generated key named ALTID across different models.

Furthermore, I get “Clustered indexes check” problems, routinely.

These issues waste A LOT of my time.

Hi,

Toad Data Modeler version 4.3 includes new verification with Quick Fixes - a way how to fix problems of the same category at once.

RE name uniqueness: If you work with objects in one model only, the verification checks for name uniqueness. If you work with multiple models, objects in one model do not know about objects in another model. Toad Data Modeler works with objects on single model level.

Fortunately, TDM is very customizable software and you can write simple macros that will rename objects according to your needs. Try to look at Productivity Macros. You will find there code that renames different types of objects. Details:
http://www.toad-data-modeler.com/help/RenameObjectsPack.aspx

There are various quick fixes for “Clustered indexes check” problems. In Verification Log, right click the problematic item and choose Quick Fixes and one of the following options:

  • Set primary key as clustered
  • Keep first found key as clustered
  • Keep first found index as clustered

Regards,

Vaclav

Vaclav - I am talking the same model. Two tables in the same model have this problem. I imagine that it’s trivial to reproduce by creating two tables in a brand new model.

Hi,

PLEASE, can you send me the sample model with two tables and describe exactly what the problem is? Thank you.

If you cannot provide sample model, please attach screenshots.

Regards,

Vaclav