I'm not sure that replication is the answer.
We have a database with all of our customer's data ServerA, and we have another database with just one customer's data ServerB.
The data is coming from an antiquated system being output to a directory on ServerA. We have a routine that runs approximately every minute it outputs the file in tab delimited format, and executes a batch file that runs sqlcmd to import the file into the database.
We are using the same command to output files for just the one customer, only the problem is, we can't move the files onto ServerB, we can't map a drive in either direction, but we can talk to the database on either server from either server.
So we could just export the data from one server to another, but the command would need to be executed from a batch file, meaning a stored .SQL script, or a stored procedure.
I considered DTS, but like replication, I don't know enough to stop it from moving ALL of the data instead of just some of the data.
I'm playing with OPENROWSET right now, I guess I was not searching for correct terminology. If this doesn't provide what we want, I will look into the linked server option.
As far as SSIS goes, I did look into it and I beleive it to be exactly what we want and need, but we're on a fairly strict timeline for this project, so tweaking and efficiency will have to come later, functionality first. (And I hate that).