May 14, 2008 at 9:58 am
I am managing the development of a database that could hold up about 18G of data. The project is evaluating the use of data persistence objects which I understand conceptually, but have not used in the development of a database system. If I understand this concept correctly the database tables become persistent data objects.
This paradigm appears to me to represent an adhoc query mechanism to the database. What I am not clear on is how this methodology compares in terms of performance to using stored procedures which represent a compiled and optimized interface to the database. The data persistence paradigm would appear to be accessing data directly requiring each data access to be parsed, etc. which would incur considerable overhead.
If anyone has experience with the use of data persistence and has information as to how this approach compares to the procedure approach in terms of performance I would appreciate some feedback. I am all for new technology but not if it will cost me in terms of performance.
May 14, 2008 at 11:44 am
We're going through similar circumstances. Look around the site here at some of the discussions on Object Relational Modeling, Hibernate, nHibernate and LINQ. I also posted some of my research at the blog linked below.
"The credit belongs to the man who is actually in the arena, whose face is marred by dust and sweat and blood"
- Theodore Roosevelt
Author of:
SQL Server Execution Plans
SQL Server Query Performance Tuning
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply