:: ::To send the data to the database, the DAL will serialize the BL's "trucks" into XML, :: ::and will send it to the Oracle DBase. :: Cough. What? Are you serious? You go all the way down into the DAL of a client/server :: application just o THEN turn around and use XML just to tranport the data into the server? I've implemented a similar design in a couple of projects. We didn't use an Oracle SP, but we did send our data (in XML) from the web-server to the database-tier. I wrote our own transaction service in C to read the XML and use OCI to insert/update/delete the data in to the database. The design was quite efficient. :: Is there any sane reason you think to have for using XML? I love :: XML, but I would never dream it up to operate on that level of my :: applications - it makes hardly any sense in the DAL. XML is slow, a ressource :: hog, clogging up network connections etc. etc.etc. Ok, it has it's :: advantages, but - frankly- thescenario you describe is exacltle one where :: XML can not use any of it's advantages and you are left with all the negatives. You overlooked one of XML's prime advantages: grouping related data into a tree. It was much more efficient to push the tree of data to a C program running on the same tier as the database, and let it handle CRUD. The larger the tree, the more appealing this design becomes.