Keeping the focus off of performance issues, since this was not one of the supervisor's requirements, I would like to point out that this change will not achieve portability. Using Microsoft supplied libraries is what most programmers use to access SQL Server from a client program, and using Oracle libraries is what you tend to use when accessing Oracle databases. Even when you use only Microsoft code, often you have to rewrite your SQL syntax to be Oracle compatible. So just saying keep all logic on the client side is not sufficient. You need to archetect and test your code against all possible targets. There are many ways to do it, and one it to develope a stored procedure library for each target database & version. Another would be to buy a 3rd party middleware package to use in client code that uses only the lowest common data types & functions that all target databases support identically with no stored procedures required, or with them suppling the procedures. Good luck with the company debates, TC