Know when to use a O/R Mapper and know when to use T-SQL

Klaus Aschenbrenner has a post today where he points out that one of his use case's where he had to update 10,000 records ended up being much faster when using T-SQL.  I think he brings up an important point.  O/R Mapper's are a great time saver, I use them on most of the work I do these days, however, I still use T-SQL as well.  Bulk updating of data is usually not a strength of an O/R Mapper so T-SQL is the better approach.  LLBLGen Pro and WilsonORMapper already have features that allow the updating of 10,000 records via their "mapper" to be converted into a single query, hopefully the makers of other O/R Mappers will follow.   Until they do make sure you know how your O/R Mapper is working behind the scenes so you know whether performing an action using you're mapper of choice or via T-SQL is the way to go!

# re: Know when to use a O/R Mapper and know when to use T-SQL

Monday, February 12, 2007 2:53 PM by 8    
86

Post a Comment

 
 
Prove you're not a spammer: 
9 + 8 =