Copy from one database table to another C#

Question

Using C# (vs2005) I need to copy a table from one database to another. Both database engines are SQL Server 2005. For the remote database, the source, I only have execute ac

Answer 1

Perhaps SqlBulkCopy; use SqlCommand.ExecuteReader to get the reader that you use in the call to SqlBulkCopy.WriteToServer. This is the same as bulk-insert, so very quick. It should look something like (untested);

using (SqlConnection connSource = new SqlConnection(csSource))
using (SqlCommand cmd = connSource.CreateCommand())
using (SqlBulkCopy bcp = new SqlBulkCopy(csDest))
{
    bcp.DestinationTableName = "SomeTable";
    cmd.CommandText = "myproc";
    cmd.CommandType = CommandType.StoredProcedure;
    connSource.Open();
    using(SqlDataReader reader = cmd.ExecuteReader())
    {
        bcp.WriteToServer(reader);
    }
}

Answer 2

Bulk Copy feature of ADO.NET might help you take a look at that :

MSDN - Multiple Bulk Copy Operations (ADO.NET)

An example article

Answer 3

I would first look at using SQL Server Intergration Services (SSIS, née Data Transfer Services (DTS)).

It is designed for moving/comparing/processing/transforming data between databases, and IIRC allows an arbitrary expression for the source. You would need it installed on your database (shouldn't be a problem, it is part of a default install).

Otherwise a code solution, given the data size (small), pull all the data from the remove system into an internal structure, and then look for rows which don't exist locally to insert.

Answer 4

Doesn’t seem to be huge quantity of data you have to synchronize. Under conditions you described (only SP to access the remote DB and no way to get anything else), you can go for Marc Gravell’s solution. In the case the data can only grow and existing data can not be changed you can compare the record count on remote and internal DB in order to optimize operation; if no change in remote DB no need to copy.

Answer 5

You probably can't do this, but if you can't, DON'T do it with a program. If you have any way of talking to someone who controls the source server, see if they will set up some sort of export of the data. If the data is as small as you say, then xml or csv output would be 100x better than writing something in c# (or any language).

So let's assume they can't export, still, avoid writing a program. You say you have more control over the destination. Can you set up an SSIS package, or setup a linked server? If so, you'll have a much easier time migrating the data.

If you set up at bare minimum the source as a linked server you could write a small t-sql batch to

TRUNCATE DestTable

INSERT INTO DestTable SELECT SourceTable.Star FROM [SourceServer].[Schema].[Table]

wouldn't be as nice as SSIS (you have more visual of what's happening, but the t-sql above is pretty clear).

Since I would not take the programming route, the best solution I could give you would be, if you absolutely had to:

Use SqlClient namespace.

So, create 2 SqlConnections, 2 SqlCommands, and get the instance of the 1 SqlReader.

Iterate through the source reader, and execute the destination SqlCommand insert for each iteration with the.

It'll be ugly, but it'll work.