Performance to write data in SQL Server 2005

Dear friends,

A simple question to you... witch of this dataflow destination is better for performance to write data in a SQL Server 2005:

1. SQL Server Destination?

2. OLEDB Destination?

3. Other?

Thanks!

This may appear to be a simple question on the surface, but there are many different variables that come into play.

From my personal experience, the SQL Server Destination component is too limited as you can only write data to SQL Server instances that are on the same machine where the package is running. This is not flexible enough to support the "real world" in which my packages need to run.

Also, performance with the OLE DB Destination is excellent. I've never done a side-by-side comparison, but I have never found a situation where the OLE DB Destination did not give me the performance I need.

Here's a few blog posts that look at this subject as well:

http://blogs.digineer.com/blogs/larar/archive/2006/08/20/385.aspx http://blogs.conchango.com/jamiethomson/archive/2006/08/14/4344.aspx