05-08-2016 11:07 AM - edited 03-14-2019 04:04 PM
Hello everyone,
this is for UCCX 11. Premium.
Need to search through a list of telephone numbers of existing customers so as to treat them differently next time they call.
Was wondering what the best approach would be, reading and searching the list directly from the external database using db steps, or have the list published in an xml (or other file) and searching through that, or ...
The list of numbers is of the order of 10,000 so processing delay (among others) could be a consideration.
Thanks in advance.
Solved! Go to Solution.
05-08-2016 07:50 PM
Well since you have a Premium license and I assume that you must have a 3rd party DB as well there so you can go for both of the options. Using DB steps keep it clean and you can pull various number of fields for a single record whereas with XML I found that a little less flexible to be honest.
Though doing it through XML means keeping the copy locally on the UCCX server hence no matter if the external DB is accessible or not that should not be a problem. That being said, in this case UCCX will be doing the processing of file and searching for the records on its own that can put extra hit on the CPU and performance which is not the case using DB steps since all the processing will be happening on an External DB
However, apart from this I really don't see a benefit of doing it through XML and not DB steps. Rest also depends on your accessibility and ease to do things as well. As far as number of records are concerned 10k is not a big number especially when I have seen people processing more than 200K records using an external DB
Regards
Deepak
05-09-2016 01:45 AM
I'd certainly be looking at a direct database integration for this. It's a much more scalable option, a huge XML file isn't something you want to be parsing through over and over for every call.
Aaron
05-08-2016 07:50 PM
Well since you have a Premium license and I assume that you must have a 3rd party DB as well there so you can go for both of the options. Using DB steps keep it clean and you can pull various number of fields for a single record whereas with XML I found that a little less flexible to be honest.
Though doing it through XML means keeping the copy locally on the UCCX server hence no matter if the external DB is accessible or not that should not be a problem. That being said, in this case UCCX will be doing the processing of file and searching for the records on its own that can put extra hit on the CPU and performance which is not the case using DB steps since all the processing will be happening on an External DB
However, apart from this I really don't see a benefit of doing it through XML and not DB steps. Rest also depends on your accessibility and ease to do things as well. As far as number of records are concerned 10k is not a big number especially when I have seen people processing more than 200K records using an external DB
Regards
Deepak
05-09-2016 01:45 AM
I'd certainly be looking at a direct database integration for this. It's a much more scalable option, a huge XML file isn't something you want to be parsing through over and over for every call.
Aaron
05-09-2016 05:16 AM
Thank you Deepak and Aaron,
Your comments make perfect sense to me.
Thanks for taking the time to respond.
05-09-2016 09:14 AM
You are welcome, glad that it helped and thanks for marking the Correct Answer.
Regards
Deepak
Discover and save your favorite ideas. Come back to expert answers, step-by-step guides, recent topics, and more.
New here? Get started with these tips. How to use Community New member guide