Hi,
I'd be keen to hear from anybody who uses QAS Batch to clean their data. It's pretty straightforward for data we're exporting in, but how do people use it to clean up their data already in Tessitura. What are the exact steps you use?
Do you clean up the address table in segments? Do you export it as a file and then re-import it? Given that the data is changing in the address table is changing all the time, I just wanted to make sure that I run it as carefully as possible.
Hi Matthew, We use QAS Batch to clean Tessitura address data on a weekly basis. The QAS Batch tool did not have enough flexibility for configuration to meet our address data entry rules, or to allow us to select only certain address record AND initial testing indicated that querying the t_address table directly was detrimental to database performance, so I designed QAS Export and Import stored procedures. The Export is pretty simple, it excludes certain addresses based on our business rules, addresses that have already been cleaned by QAS, junk addresses, vanity addresses etc. It also records a datetime stamp for use later in the Import. We control which addresses are included in the Export with parameters for List, Addresses updated from/to, Inactive and Address Type. We save the output as a text file. We then clean the addresses in QAS Batch, and commit changes back to the text file. The QAS Import stored procedure then applies formatting that fixes some QAS inconsistencies, and does error checking, the main aspect being addresses that have been updated in the database since Export (referencing the datetime stamp), before updating the cleaned addresses in the database. If you are interested I would be happy to share our QAS Export and Import procedures. I have configured the Export so it can be run from the client. At this stage the Import is run in a SQL query only. Cheers Kim
Hi Matthew,
We use QAS Batch to clean Tessitura address data on a weekly basis.
The QAS Batch tool did not have enough flexibility for configuration to meet our address data entry rules, or to allow us to select only certain address record AND initial testing indicated that querying the t_address table directly was detrimental to database performance, so I designed QAS Export and Import stored procedures.
The Export is pretty simple, it excludes certain addresses based on our business rules, addresses that have already been cleaned by QAS, junk addresses, vanity addresses etc. It also records a datetime stamp for use later in the Import. We control which addresses are included in the Export with parameters for List, Addresses updated from/to, Inactive and Address Type. We save the output as a text file.
We then clean the addresses in QAS Batch, and commit changes back to the text file.
The QAS Import stored procedure then applies formatting that fixes some QAS inconsistencies, and does error checking, the main aspect being addresses that have been updated in the database since Export (referencing the datetime stamp), before updating the cleaned addresses in the database.
If you are interested I would be happy to share our QAS Export and Import procedures. I have configured the Export so it can be run from the client. At this stage the Import is run in a SQL query only.
Cheers
Kim
Hi Matthew
We recently got QAS Batch and have done a couple of tests to export existing records out of Tessitura, run them through QAS Batch and import the data. We have been using the NCOA Utility to be the link between Tessitura and QAS. Weve only been testing but it does seem to be working very well.
Let me know if you need more info.
Mark