>
>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.