I've followed the steps in an attempt to replicate to & from the DMZ sql server.
It's a one-way trust.
Replication, Trans. Repl w/ Immediate Update is setup
My domain sql server can replicate to the dmz, but when I try to change something at the subscriber it tells me
"SQL Server not found or access denied"
I have attempted everything from the article on Replication Answers.
Server is in hosts file
I setup an alias in Client Network utilities using the IP Address that I input in the hosts file
What else can I do to replicate back from the DMZ? What am I missing?
JLS,
is the client alias the same name as the servername?
Can you try establishing client connectivity using query analyser on the subscriber to the sql server?
Can you ping the publishing sql server from the subscriber?
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)
|||Paul,
Thanx for answering. It seems the problem was with the firewall port & that has been fixed, but now I get a Login failed for user SA.
I am not using SA for this publication / subscription. I am using Sql Authentication & have setup a new account on each box called dmzrepl.
I also tried to do a linked server query & receive the exact same message about sa login failing.
What in the world am I missing?
jls
"Paul Ibison" <Paul.Ibison@.Pygmalion.Com> wrote in message news:e5tvXzH7FHA.1864@.TK2MSFTNGP12.phx.gbl...
JLS,
is the client alias the same name as the servername?
Can you try establishing client connectivity using query analyser on the subscriber to the sql server?
Can you ping the publishing sql server from the subscriber?
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)
|||JLS,
I think you're almost there. Have a look at this article for the next stage: http://support.microsoft.com/default...b;en-us;320773
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)
|||YIKES! I was afraid you were going to point me in that direction....
I found this in my searching & tried it, to no avail. I am still receiving sa login failed even after following the workaround.
Any other ideas?
jls
"Paul Ibison" <Paul.Ibison@.Pygmalion.Com> wrote in message news:eAA0tpI7FHA.3136@.TK2MSFTNGP09.phx.gbl...
JLS,
I think you're almost there. Have a look at this article for the next stage: http://support.microsoft.com/default...b;en-us;320773
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)
|||I don't believe this will work. MSDTC needs RPC ports open for inbound
traffic on both sides of your DMZ.
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
"JLS" <jlshoop@.hotmail.com> wrote in message
news:ue1ctaF7FHA.3880@.TK2MSFTNGP12.phx.gbl...
I've followed the steps in an attempt to replicate to & from the DMZ sql
server.
It's a one-way trust.
Replication, Trans. Repl w/ Immediate Update is setup
My domain sql server can replicate to the dmz, but when I try to change
something at the subscriber it tells me
"SQL Server not found or access denied"
I have attempted everything from the article on Replication Answers.
Server is in hosts file
I setup an alias in Client Network utilities using the IP Address that I
input in the hosts file
What else can I do to replicate back from the DMZ? What am I missing?
|||JLS,
please see Hilary's post. Looks like you need to open up RPC over TCP\IP and add another rule to the firewall. These links will hopefully help:
http://support.microsoft.com/default.aspx?kbid=841251
http://www.windowsitpro.com/Article/...412/13412.html
Paul Ibison
|||Paul / Hilary,
Thanx for the answers, I appreciate it. With the answer being to open RPC ports, I think we will rethink this project, as that will open a security hole we don't want open.
"Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message news:uhvxlPM7FHA.444@.TK2MSFTNGP11.phx.gbl...
I don't believe this will work. MSDTC needs RPC ports open for inbound
traffic on both sides of your DMZ.
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
"JLS" <jlshoop@.hotmail.com> wrote in message
news:ue1ctaF7FHA.3880@.TK2MSFTNGP12.phx.gbl...
I've followed the steps in an attempt to replicate to & from the DMZ sql
server.
It's a one-way trust.
Replication, Trans. Repl w/ Immediate Update is setup
My domain sql server can replicate to the dmz, but when I try to change
something at the subscriber it tells me
"SQL Server not found or access denied"
I have attempted everything from the article on Replication Answers.
Server is in hosts file
I setup an alias in Client Network utilities using the IP Address that I
input in the hosts file
What else can I do to replicate back from the DMZ? What am I missing?
Showing posts with label trans. Show all posts
Showing posts with label trans. Show all posts
Friday, March 30, 2012
Friday, March 9, 2012
Replication on 130GB db
Is there anyone with some expirience in replicating such large database?
Maybe some good link or something like that. I would need trans replication
instructions.
regards,
DaliborIf you have a fast link between your publisher/distributor/subscriber,
replicating 130GB is still managble, especially when the amount of data
changes is relatively small in comparison with the total database size. We
are replicating bigger database than that with transactional replication.
With 130GB of data, it could be a major headache to re-snapshot your
publication, which may take a while in most environments. It can become a
major problem when you don't have a large maintenance window. For us, the
most common reason for requiring a new snapshot is new releases of the
application that introduce database schema changes. Once we have reined in
the developers and cut down the frequency of releases, we have been able to
support replicating 200~300GB databases.
--
Linchi Shea
linchi_shea@.NOSPAMml.com
"Dalibor Cvijetinovic" <dalibor@.ice.si> wrote in message
news:OC8DqnatDHA.2340@.TK2MSFTNGP12.phx.gbl...
> Is there anyone with some expirience in replicating such large database?
> Maybe some good link or something like that. I would need trans
replication
> instructions.
> regards,
> Dalibor
>|||Our amount of data that needs to be replicated is around 20-30GB. That is
the reason why I would like to change replication type.Currently I am using
snapshot/push replication. Our maintenance window is around 12 hours. But in
that time i must import some data which takes about 2 hours and then i do
snapshot/push replication of 130GB. That replication is lasting forever!!
After that i must replicate another db with 25GB.
I need to make trans replication or I will simply get ...
Furthere more this large scaled replication are not stable.
Can you give me some pointers on how to resolve this problem.
Dalibor
"Linchi Shea" <linchi_shea@.NOSPAMml.com> wrote in message
news:Ol$yrMbtDHA.424@.TK2MSFTNGP11.phx.gbl...
> If you have a fast link between your publisher/distributor/subscriber,
> replicating 130GB is still managble, especially when the amount of data
> changes is relatively small in comparison with the total database size. We
> are replicating bigger database than that with transactional replication.
> With 130GB of data, it could be a major headache to re-snapshot your
> publication, which may take a while in most environments. It can become a
> major problem when you don't have a large maintenance window. For us, the
> most common reason for requiring a new snapshot is new releases of the
> application that introduce database schema changes. Once we have reined in
> the developers and cut down the frequency of releases, we have been able
to
> support replicating 200~300GB databases.
> --
> Linchi Shea
> linchi_shea@.NOSPAMml.com
>
> "Dalibor Cvijetinovic" <dalibor@.ice.si> wrote in message
> news:OC8DqnatDHA.2340@.TK2MSFTNGP12.phx.gbl...
> > Is there anyone with some expirience in replicating such large database?
> > Maybe some good link or something like that. I would need trans
> replication
> > instructions.
> >
> > regards,
> > Dalibor
> >
> >
>
Maybe some good link or something like that. I would need trans replication
instructions.
regards,
DaliborIf you have a fast link between your publisher/distributor/subscriber,
replicating 130GB is still managble, especially when the amount of data
changes is relatively small in comparison with the total database size. We
are replicating bigger database than that with transactional replication.
With 130GB of data, it could be a major headache to re-snapshot your
publication, which may take a while in most environments. It can become a
major problem when you don't have a large maintenance window. For us, the
most common reason for requiring a new snapshot is new releases of the
application that introduce database schema changes. Once we have reined in
the developers and cut down the frequency of releases, we have been able to
support replicating 200~300GB databases.
--
Linchi Shea
linchi_shea@.NOSPAMml.com
"Dalibor Cvijetinovic" <dalibor@.ice.si> wrote in message
news:OC8DqnatDHA.2340@.TK2MSFTNGP12.phx.gbl...
> Is there anyone with some expirience in replicating such large database?
> Maybe some good link or something like that. I would need trans
replication
> instructions.
> regards,
> Dalibor
>|||Our amount of data that needs to be replicated is around 20-30GB. That is
the reason why I would like to change replication type.Currently I am using
snapshot/push replication. Our maintenance window is around 12 hours. But in
that time i must import some data which takes about 2 hours and then i do
snapshot/push replication of 130GB. That replication is lasting forever!!
After that i must replicate another db with 25GB.
I need to make trans replication or I will simply get ...
Furthere more this large scaled replication are not stable.
Can you give me some pointers on how to resolve this problem.
Dalibor
"Linchi Shea" <linchi_shea@.NOSPAMml.com> wrote in message
news:Ol$yrMbtDHA.424@.TK2MSFTNGP11.phx.gbl...
> If you have a fast link between your publisher/distributor/subscriber,
> replicating 130GB is still managble, especially when the amount of data
> changes is relatively small in comparison with the total database size. We
> are replicating bigger database than that with transactional replication.
> With 130GB of data, it could be a major headache to re-snapshot your
> publication, which may take a while in most environments. It can become a
> major problem when you don't have a large maintenance window. For us, the
> most common reason for requiring a new snapshot is new releases of the
> application that introduce database schema changes. Once we have reined in
> the developers and cut down the frequency of releases, we have been able
to
> support replicating 200~300GB databases.
> --
> Linchi Shea
> linchi_shea@.NOSPAMml.com
>
> "Dalibor Cvijetinovic" <dalibor@.ice.si> wrote in message
> news:OC8DqnatDHA.2340@.TK2MSFTNGP12.phx.gbl...
> > Is there anyone with some expirience in replicating such large database?
> > Maybe some good link or something like that. I would need trans
> replication
> > instructions.
> >
> > regards,
> > Dalibor
> >
> >
>
Replication of Triggers
If I create a trigger on a table that is already in a Trans Pub, will
the trigger be replicated?
IF so how can I prevent this?
I have different triggers that affect different tables on the
subscriber and the publisher.
TIA,
Larry...
No, the trigger won't get replicated.
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)
|||Triggers will be replicated if a new snapshot is generated and you have
elected to replicate User Triggers and you have issued an
sp_refreshsubscriptions.
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
"LPR-3rd" <lreames@.gmail.com> wrote in message
news:1129581351.100366.214720@.g49g2000cwa.googlegr oups.com...
> If I create a trigger on a table that is already in a Trans Pub, will
> the trigger be replicated?
> IF so how can I prevent this?
> I have different triggers that affect different tables on the
> subscriber and the publisher.
> TIA,
> Larry...
>
|||thanks guys
the trigger be replicated?
IF so how can I prevent this?
I have different triggers that affect different tables on the
subscriber and the publisher.
TIA,
Larry...
No, the trigger won't get replicated.
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)
|||Triggers will be replicated if a new snapshot is generated and you have
elected to replicate User Triggers and you have issued an
sp_refreshsubscriptions.
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
"LPR-3rd" <lreames@.gmail.com> wrote in message
news:1129581351.100366.214720@.g49g2000cwa.googlegr oups.com...
> If I create a trigger on a table that is already in a Trans Pub, will
> the trigger be replicated?
> IF so how can I prevent this?
> I have different triggers that affect different tables on the
> subscriber and the publisher.
> TIA,
> Larry...
>
|||thanks guys
Subscribe to:
Posts (Atom)