Question

I want to migrate data from one database to another database in Microsoft SQL Server 2005. I need to verify those rows retrieved before I insert them to the destination database's tables. Which approach is reasonable for this kind of things?

I am trying to use two datasets in my VB.NET program. Is it reasonable? Can you suggest me?

Thanks in advance,

RedsDevils

Was it helpful?

Solution

It depends on how much data you're talking about, but I'd tend to pass on .Net datasets for a migration task, as that means pulling all the data into memory. If you must do this via a .Net client program, at least use a DataReader instead. But what's even better is to keep it all in Sql Server via Sql Server Integration Services.

Licensed under: CC-BY-SA with attribution
Not affiliated with StackOverflow
scroll top