So, the final recipe looks like following:

For Insert and Update calculate the hash e.g. with MD5 and put it in Hash property. Index it with not unique index.

Find duplicates with SQL query on Hash where group by for hash shows more than one occurrence.

Loop through all the values with same hash just and check Text property values to be sure that they are duplicates but not hash collisions.

Thanks, Alex, Dmitry, Robert!

Hi, Lin!

You are creating this calculated dimensions as shared members. In this case, they are stored in some ^DeepSee.* global.

One of the options to avoid calculated dimensions' storage in the global and further deployment difficulties you can use calculated members with Shared Storage option turned off.

You can alter this option if you create calculated dimension in a named and saved pivot.

In this case, the calculated measure definition will be placed directly in the MDX query of this pivot thus you don't need to deploy it, cause it will live with the pivot.