I am doing a huge database cleanup. In our old system, it was ok for 10 constituent records to all have the same email address attached to them...in Tessitura, it is not. We found that out the hard way, so now I am trying to manually go through and take all the emails off of the constituent records that they don't belong on.
Our Ongoing Services team sent me a list they pulled of all the constituents with the same emails that kept their logins, which I have already gone through. They also pulled us a list of every account they pulled the temp logins off of, but did not specify the duplicate emails. So I have a list of about 90,000 email addresses I am tediously going through to see if each email has multiple records attached to it. Since many do not, it's wasting my time to check those ones.
I have a ticket open about this but haven't heard back in a few days; I'm wondering if there is a list or an extraction or something I can pull myself to get the data I am looking for.
What I am looking for is a list of all of our constituent records that no longer have logins attached, but do have email addresses and that email address is linked to multiple constituent records. Is it doable myself or do I have to wait and have Ongoing Services do it?
A list or an extraction is only going to give you a list of customer numbers, so I could put together a manual query list for you that would give you all the constituent ids of customers who share an email address with another customer, but it wouldn't tell you which email address it was or who the other customers were. So, better than checking every email address, but...
Yeah, we just wrote a custom report to tackle this particular area.
Ah, yeah not that helpful either. Maybe I will have to wait for Ongoing Services to pull it. Attached is what they sent me (don't mind my highlights, it's how I kept it all straight). I was kind of hoping to pull something similar myself, but it doesn't appear possible.
(file has been removed)
Gawain Lavers said:I could put together a manual query list
Hah, I've been poking around with it, and I can't think without CTEs anymore.
LOL. I hear ya there. I know I've used CTE's when I really didn't need to. Sometimes it is just easier to break up the logic into CTE parts and then put it all together at the end.
It's okay, I can do the same thing with a subquery of a subquery of a subquery and then copy and paste that in five different places.