※ Download: The create unique index statement terminated because a duplicate key was found for the object name
The duplicate key value is 0000001414. You can't post or upload images. The duplicate key value is 100. FKId GROUP BY A, B, Year, t1.
You can't edit other topics. Most significant primary key is... You can't post topic replies.
- Resolution: Error of the Severity Level 16 are generated by the user and can be fixed by the SQL Server user.
One of the most common headaches experienced when you upgrade Dynamics AX is unique index errors, so I wrote a little sql script to fix those. This commonly experienced with date effective tables or tracking tables in general. In fact, if you upgrade the AX database from CU6 to CU7 on the sample Contoso image, you will experience this. More particularly, you will get these types of errors when you try to synchronize: Error Synchronize database Cannot execute a data definition language command on. The SQL database has issued an error. The duplicate key value is 5637144577, 0, 0, 22565423328, Jan 1 1900 12:00AM, Jan 1 1900 12:00AM, 0. HCMPOSITIONFORECASTBUDGETACCTLINE PARTITION,POSITIONFORECASTSCENARIO,BUDGETPURPOSETYPEDETAIL,LEGALENTITY,EFFECTIVEDATE,EXPIRATIONDATE,ISSYSTEMGENERATED Error Synchronize database Cannot execute a data definition language command on. The SQL database has issued an error. The duplicate key value is 5637144577, 0. HCMPOSITIONFORECASTLASTMODIFIED PARTITION,POSITIONFORECASTSCENARIO Error Synchronize database Problems during SQL data dictionary synchronization. Info Synchronize database Synchronize failed on 2 table s Background: Date-Effective tables are a big deal. They allow you to track the history of when a record is valid for example. For example, if a customer changes address, you may want to be able to record that a customer lived in Oklahoma from June 2002 till June 2006 and Texas from 2006 till current. You can see why these are so important. But to make this happen, fundamental changes needed to be introduced in tables. The problem with this is that AX populates the record dates as January 1 st 1900 for records that existed before time recording was introduced. Solution: since 1900 is just a dummy value, keep on populating the date-effective tables with dummy values for historical data that existed before the real data starts coming in. You just need to tell everyone that anything in 1900 should not be assumed to be a real data year.
The AOS version is RTM with CU3. Msg 1505, Level 16, State 1, Line 2 The CREATE UNIQUE INDEX statement terminated because a duplicate key was found for the object name 'dbo. The SQL database has issued an error. The SQL database has issued an error. You can't edit other events. You can't post new topics. The duplicate key value is Value1, Value2. The duplicate key value is 5637144577, psus. A little bit of this and a little byte of that can cause bloatware.
