For various reasons we have a modest number of duplicate E-Addresses (T_EADDRESS) in Tessitura, and will continue to do so. This is a particular issue when doing customer merges, and I want to insert a procedure to help clear up this issue.
I won't go into the complex process for choosing which E-Address to keep, or which standard E-Address features to consolidate in the remaining address. The thing I'm worried about is deleting the redundant email addresses.
I'm already working on merging over connected Logins and Communication Point Preferences. But it occurs to me that a great deal else may be attached to the other email addresses: T_PROMOTION and T_ORDER at least. Elsewhere? Since the eaddress_no columns often allow nulls I'm guessing a SQL tool is unlikely to give me everything. Does anyone have a good list?
Thanks,
Gawain
What I can find with an eaddress_no column is:
The last two are both empty in our database, and I'm not sure what the TM_ and TS_ prefixes denote. T_PROMOTION which I mentioned earlier is actually "eaddress" and stores the T_EADDRESS.address value, as does LT_HARDBOUNCE, so those I can ignore.