title: Need help designing big database update process
body: <p>We have a database with ~100K business objects in it. Each object has about 40 properties which are stored amongst 15 tables. I have to get these objects, perform some transforms on them and then write them to a different database (with the same schema.)
  This is ADO.Net 3.5, SQL Server 2005.</p>
  
  <p>We have a library method to write a single property. It figures out which of the 15 tables the property goes into, creates and opens a connection, determines whether the property already exists and does an insert or update accordingly, and closes the connection.</p>
  
  <p>My first pass at the program was to read an object from the source DB, perform the transform, and call the library routine on each of its 40 properties to write the object to the destination DB. Repeat 100,000 times. Obviously this is egregiously inefficent.</p>
  
  <p>What are some good designs for handling this type of problem?</p>
  
  <p>Thanks</p>