Creating a table in the following manner
create table dbo.test ( w int, x int, y int, z int) CREATE INDEX [IX_XXXX_X] ON [dbo].[TEST](x ASC, y ASC) INCLUDE(w,z) ON [PRIMARY]
Then running data model scan will yield the following error
(1) job: 2773 profile: SQL_XXXXXXX10025319_ASTERIX_SRC : failed to get metadata for conprof: SQL_XXXXXXX10025319_ASTERIX_SRC with exception: InvalidDataAccessApiUsageException: Multiple representations of the same entity [com.ca.tdm.datadiscovery.jpa.DBDataDiscoveryUniqueKey#com.ca.tdm.datadiscovery.jpa.DBDataDiscoveryUniqueKeyPK@9c1b66ed] are being merged. Detached: [DBDataDiscoveryUniqueKey{entityId=2672264, keyName='IX_XXXX_X', columnPos=0, columnName='w', keyType=I}]; Detached: [DBDataDiscoveryUniqueKey{entityId=2672264, keyName='IX_XXXX_X', columnPos=0, columnName='z', keyType=I}], (2) Failed to scan entities for profile SQL_XXXXXXX10025319_ASTERIX_SRC, reason: TDMDatabaseException: job: 2773 profile: SQL_XXXXXXX10025319_ASTERIX_SRC : failed to get metadata for conprof: SQL_XXXXXXX10025319_ASTERIX_SRC with exception: InvalidDataAccessApiUsageException: Multiple representations of the same entity [com.ca.tdm.datadiscovery.jpa.DBDataDiscoveryUniqueKey#com.ca.tdm.datadiscovery.jpa.DBDataDiscoveryUniqueKeyPK@9c1b66ed] are being merged. Detached: [DBDataDiscoveryUniqueKey{entityId=2672264, keyName='IX_XXXX_X', columnPos=0, columnName='w', keyType=I}]; Detached: [DBDataDiscoveryUniqueKey{entityId=2672264, keyName='IX_XXXX_X', columnPos=0, columnName='z', keyType=I}]: Exception raised: TDMDatabaseException: job: 2773 profile: SQL_XXXXXXX10025319_ASTERIX_SRC : failed to get metadata for conprof: SQL_XXXXXXX10025319_ASTERIX_SRC with exception: InvalidDataAccessApiUsageException: Multiple representations of the same entity [com.ca.tdm.datadiscovery.jpa.DBDataDiscoveryUniqueKey#com.ca.tdm.datadiscovery.jpa.DBDataDiscoveryUniqueKeyPK@9c1b66ed] are being merged. Detached: [DBDataDiscoveryUniqueKey{entityId=2672264, keyName='IX_XXXX_X', columnPos=0, columnName='w', keyType=I}]; Detached: [DBDataDiscoveryUniqueKey{entityId=2672264, keyName='IX_XXXX_X', columnPos=0, columnName='z', keyType=I}]
We where able to workaround this error by disabling that index. But still it's a regression from 4.11.4007
TDM Portal 4.11.5030.0
Database is SQL Server
Model scanning could fail for SQL Server tables with indexes with included columns.
This was fixed in version TDMWeb-4.11.5034.0.zip, so apply the latest patch and re-test.
Refer to this KB for how to apply TDM Patches: How to apply patches for TDM