You need to consider information none of us will have available.
<ul type="square">[*]What is the programming skill set in your department?[*]What is your infrastructure use? Are you already set up for a specific technology?[*]Are you wanting to bring in a thrid party end-user mimic tool, or are you wanting to do back end only?[*]Would a scripting language like PERL or PYTHON do what you need? [*] How indepth are you wanting to test? Could a simple in-code unit tester do the job, or are you looking to do full load/performance/etc testing?[*]If you only have those two items, listed as your test, what do you already have inhouse you can use with miniumal training or learning curve?[/list]
Thank you Rich & Tony for your inputs. As Rich suggested, we decided to do the first validation manually to get a baseline xml and database which can be used for comparisons against the actual xml and database in automated tests. We have also figured out that QTP does provide featurs to compare an XML to XML and DB to DB, so will be using QTP as automation tool.