Sql-server – transaction log restore

editted based on feedback in comments

1. If you could stay readonly than a good alternative to replication could be log shipping. The vendor would create transaction log backups. And send those backup to you. You then apply those backups.You can't restore differential only, you would still need to reply a full first. Another benefit of (delayed) logshipping is that, since the source is at the vendor (where you have no control over what they do with it, you might want to build in some buffer (in time) that when they make a huge mistake, you simply pause the logshipping redo, so you still have a good copy)
2. For restoring filegroups/files you need transaction log restores as well. It can work but it highly depends on the growth rate vs the transaction log rate if I would prefer this above option 1, simply log shipping. Furhtermore, partitioning your database and table just for the sole purpose of solving your replica problem wouldn't be the route I would pick first but I have some questions for you later.
3. Replication sounds like a very good option if you think the restoring of transaction log backups becomes to much work.
4. What prohibits sql 2000 from doing Bulk Inserts? However, if you think logshipping is tedious, keeping track of updating every single object sounds like a potentially more troublesome strategy.
5. I have no experience with cdc. somebody else has to help out on that.

Couple of questions for you:

1. How big is the initial database size?
2. What will be the daily, monthly growth rate?
3. What will be the daily growth rate of the transaction log?
4. is it possible to have both locations in the same domain?
5. Is it possible to build a secure connection between the two locations?
6. What is the bandwidth between the to locations? what is the latency?

If we have some numbers, it's easier to provide you with a better advise.

The user has to be granted permissions in the source copy of the database.

The restored copy is just that -- a copy -- of the source, so there's no way to change one and not the other.

Since this is a SQL Server login, you'll need to create the logins on both servers with identical SIDs so the mapping from the database user to the login matches in all cases. You can do this by recreating the login on the secondary, specifying the SID manually in the CREATE LOGIN statement.

If you went with a solution such as replication (not saying you should, just giving an example), this works using two read/write databases, where you could grant permissions completely independently.