That's why I suggested a web service method - by which each db could employ whatever methodologies they have available - where the front end could run the same transaction sets thru different back end API sets.
An example API might be "Book Order" or "Ship Order" for example. I would imagine a full suite of transaction tests would also include the transactions to populate a "test" database with objects such as "Customers" "Items" etc etc. Just a thought. -----Original Message----- From: [EMAIL PROTECTED] [mailto:[EMAIL PROTECTED] On Behalf Of Geoffrey Mitchell Sent: Monday, July 16, 2007 2:47 PM To: u2-users@listserver.u2ug.org Subject: Re: [U2] UniData 7.1 vs. MS SQL 2005 performance How does not being able to know how the data is stored prohibit empirical testing? As long as you can provide inputs to a system and retrieve outputs you can perform empirical tests. -- Geoffrey Mitchell Programmer/Analyst Home Decorator's Collection 314-684-1062 ------- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/ ------- u2-users mailing list u2-users@listserver.u2ug.org To unsubscribe please visit http://listserver.u2ug.org/
