Hi All,
Has anyone else run into any issues with the potential duplicates procedure not seeming to identify duplicates?
My organization recently updated to 16.0.11 and it looks like something might have broke. I believe the token identification got updated after this update. Looking at the Duplicate Matching setting in the T_DEFAULTS table it looks lie it changed. All of the info I'm seeing in the help document says that its normally set to fname=1, lname=20, postal_code=3, street1=3 but it is currently set to fname=3, lname=20, postal_code=10, street1=10. I didn't make any manual changes to this setting.
My Potential Duplicates list is also empty even though there are definitely duplicates in our database. Is anyone else having this issue? I'm wondering if its a known issues on 16.0.11 or if I'm special for some reason.
Let me know if you need any additional info.
Thanks,
Zach
Hi Zach,I can't speak to the first part of your question because we're not on 16, but the second - have you double-checked that the identify duplicates procedure is running? There have been a few times for me where I've done an update and then for some reason, some of my daily sql jobs never restarted.
Would you be able to guide me to where I can figure out which procedures have run? I have access to the procedure in SSMS. Is there a report either in Tess or somewhere in SMSS that I can check that?
I believe Kathleen is referring to confirming the SQL Server Agent Job(s) have been running.You can right-click on the Job to view the History of the Job.You can confirm if the Job and all the Steps successfully ran.
Hmmmmmmm...
I was able to find and get to that screen but it looks like my Job History is empty. So that seems like a problem that will need to be fixed. Im guessing I will need to reach out to Tessitura about this. We updated on 2/6 so I'm guessing that any jobs that were previously scheduled haven't been running since then. Looking through the SQL Agent Category the last time anything was run was on 2/6. That might be correct for that section but the fact that there is no Job History seems wrong.
Try using the Object Explorer.
Yeah nothing in the Jobs folder either. I don't know what happened. The Duplicate ID report worked before the update. I will get ahold of Tess to see what happened. The fact that the folder is completely empty has me worried that there were other jobs that are missing now as well. Thanks for the lesson everyone! Let me know if you have any other tips on where to look.
I wonder if you do not have rights to view the Jobs folder. If you are not self-hosted, you could put in a Ticket with support to get access. This assumes that whomever at your organization that can approve things is ok with that.