>>
>>First, thank you. But these SQL Server databases are on different servers (different companies). So I don't think the above syntax will work.
>
>
>If they are on different servers, I'd take the opportunity to look at SSIS.
>
>You can build a very simple SSIS package that defines the source connection, the destination connection, and a data flow pipeline to copy the data from the source to the destination.
>
>As a matter of fact, if you use the SQL Server Import/Export wizard to define the source/destination, the wizard gives the option to generate a basic SSIS package.
Hi Kevin,
Do I understand correctly that in order for the above approach to work, using SSIS package, both servers have to be on the same network? That is, the data would go from one server to another via network connection? Or the data can be copied from one network to another?
Thank you
"The creative process is nothing but a series of crises." Isaac Bashevis Singer
"My experience is that as soon as people are old enough to know better, they don't know anything at all." Oscar Wilde
"If a nation values anything more than freedom, it will lose its freedom; and the irony of it is that if it is comfort or money that it values more, it will lose that too." W.Somerset Maugham
