Problem solve Get help with specific problems with your technologies, process and projects.

Publisher residing on a different domain

Monitoring and Administration expert Kevin Kline discusses the obstacles of database administration when a publisher resides on a different domain.

I am trying to set up a replication solution where the publisher resides on a different domain that I have no control over. The company that owns that domain will only give me read-only access to the database. I have given them database owner access to the distribution database for their server.

The idea is that they would set up the publication so the snapshots are FTPed to our distributor. The problem is that since I only have read-only access and the distributor is on our side, I cannot monitor or kick off the snapshot agent. Is there any way I can get around it without having to be system administrator or the database owner? Also, is there a way I can get SQL to compress large snapshots?

This is a rather strange situation. Why put the publisher on the other side of the domain and not on the same box as the distributor? Then things would work much easier. If they won't do that, then they should set up a domain trust so you can use regular transaction replication and perform routine maintenance.

If that's impossible, then you have some obstacles to overcome. In a situation like yours, you might wish to FTP the files (possibly zipped before sending them) and load them on a pub/dist on your side of the domain. I personally wouldn't accept the responsibility for maintaining a system that I couldn't monitor or control.


Do you have comments on this Ask the Expert Q&A? Let us know.

Dig Deeper on Microsoft SQL Server Installation

Have a question for an expert?

Please add a title for your question

Get answers from a TechTarget expert on whatever's puzzling you.

You will be able to add details on the next page.

Start the conversation

Send me notifications when other members comment.

Please create a username to comment.