BatchDestination - ADO.Net ConnectionManager

Oct 26, 2010 at 4:43 AM

Just quick question for anyone who has used this component a lot on large datasets.

Is the performance degradation with ADO.Net significant compared to OleDB? If almost all of my data (possibly 1 million records) will be inserts rather than updates should I consider having 1 OleDB CM for the insert and 1 Ado.Net CM for the updates to the same destination?


Nov 3, 2010 at 2:25 AM

I've used it on some fairly large datasets without noticing a problem, but I've never down a full comparision of the performance. One thing to note though, is that if you are going against SQL Server, there's not a huge amount of overhead in using the ADO.NET SQL Provider.

As with most performance related questions, though, the best thing to do is run some comparisions in your environment.