I have a situation where a client connects to our network via VPN has set up
a SQL Server on a small workgroup that wishes to subscribe (via
transactional replication) to publications on my SQL Publisher.
My stumbling block is permissions to the \\myserver\repldata folder on our
domain. The client machine being a non-trusted domain (in fact not even a
domain) means I can't set up read and list files & folders permissions.
My plan is that I set up the pull subscriptions, create the snapshots and
then copy the entire \\myserver\repldata folder to the client machine and
point the pull subscriptions there.
Is this the best solution in the circumstances? After the initial snapshot,
does transactional replication ever need to access \\myserver\repladat
again?
Cheers!
Simon
Simon,
you can use the alternative snapshot location option - I do it this way for
large snapshots which I zip up before sending over.
If FTP is available this is probably an easier option though to set up the
publication.
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com
|||Many thanks.
"Paul Ibison" <Paul.Ibison@.Pygmalion.Com> wrote in message
news:OzVonAjYHHA.208@.TK2MSFTNGP05.phx.gbl...
> Simon,
> you can use the alternative snapshot location option - I do it this way
> for large snapshots which I zip up before sending over.
> If FTP is available this is probably an easier option though to set up the
> publication.
> Cheers,
> Paul Ibison SQL Server MVP, www.replicationanswers.com
>
|||Try to use pass-through authentication. This is where you have two identical
local machine accounts with the same name and the same password.
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"Simon" <simon.gladwell@.gmailNotThisBit.com> wrote in message
news:%23W9Y9siYHHA.448@.TK2MSFTNGP04.phx.gbl...
>I have a situation where a client connects to our network via VPN has set
>up a SQL Server on a small workgroup that wishes to subscribe (via
>transactional replication) to publications on my SQL Publisher.
> My stumbling block is permissions to the \\myserver\repldata folder on our
> domain. The client machine being a non-trusted domain (in fact not even a
> domain) means I can't set up read and list files & folders permissions.
> My plan is that I set up the pull subscriptions, create the snapshots and
> then copy the entire \\myserver\repldata folder to the client machine and
> point the pull subscriptions there.
> Is this the best solution in the circumstances? After the initial
> snapshot, does transactional replication ever need to access
> \\myserver\repladat again?
> Cheers!
> Simon
>
|||That works when I log on that account and browse to the folder. Should I
then run SQL Server and Agent under that local account?
"Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message
news:OiI0V2jYHHA.4308@.TK2MSFTNGP05.phx.gbl...
> Try to use pass-through authentication. This is where you have two
> identical local machine accounts with the same name and the same password.
> --
> Hilary Cotter
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
|||Yes!
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"Simon" <simon.gladwell@.gmailNotThisBit.com> wrote in message
news:eQmS6QlYHHA.4692@.TK2MSFTNGP04.phx.gbl...
> That works when I log on that account and browse to the folder. Should I
> then run SQL Server and Agent under that local account?
> "Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message
> news:OiI0V2jYHHA.4308@.TK2MSFTNGP05.phx.gbl...
>
