I have SQL running on SBS Server A. It is a publisher and a distributor of a
database that has 1 subscriber a SQL Server running on SBS Server 2. How does
one replicate in a untrusted enviroment.
there was also a free ware dll that allowed sql to invoke the ras dialer..
does anyone have the valid url to this?
-- Current Standings (taken from my post on the SBS Site) --
I posted on the SQL server site and was referred to Q321822. This Q article
had only 2 paragraphs that mentioned connection between 2 non-trusted
domains. essentially it suggested creating a server agent account on both
machines. it says you 'must set up pass through authentication'. There is was
some data missing from the article.
1) How do you set up 'pass through authentication" via a SQL Agent Account?
2) Assuming 'Pass Through' is enabled, how does one reference the SBS Server?
a) 'Local Area Connection' IP Address (not likely) 192.168.0.2 (private)
b) Local Server Name. MyServer
c) FQDN MyCompany.MyServer.
d) Public Resolvable Domain Name MyCompany.com
i) With extension .com
ii) Without extension
e) Network Connection IP Address of Server 68.XXX.XXX.217 (Public)
None of the above options worked for me, response "Server doesn't exsist or
Access denied" (which is it? MDAC doesn't even know if the Server Exists?
What’s with that?)
I found the information sources lacking. None seemed to illustrate a Point A
to Point Z scenario on SBS. This is not a Version 1 product and being that
trusts are not allowed it's conceivable that many companies would be
attempting non-trusted replication.
PS, I've checked Kbase, SQL BOL, 4 MVP sites, Newsgroups, Online Concierge
and SSWUG. I was exposed to answer bits, in addition to the above mentioned
options, there was mentioned RPC over TCP, RPC over UDP, Linked server
options, Remote server options, SSL options, replication via Backup and
Restore, replication via output files, Replication via terminal services
etc..
Now, I'm a person of reasonable intelligence, willing to the put the time
and effort into research, but am I wrong here when I suggest that the
documentation is all over the map? I will be posting this reply in both the
SQL Connectivity and SQL Replication newsgroups. In my opinion Microsoft does
a great job of documenting the scope and detail of it's technologies but
often falls short when it comes to implementation documentation. They are 2
distinct types of technical writing. I love Microsoft products and take the
time to scribe my opinion in hopes that it will yield stronger product line.
With that said, I ask again for a -concise, thorough, list of steps on how
to set up a push transaction based SQL replication subscription between 2
Non-trusted Small Business Servers?
"Mario Michela" wrote:
> I have SQL running on SBS Server A. It is a publisher and a distributor of a
> database that has 1 subscriber a SQL Server running on SBS Server 2. How does
> one replicate in a untrusted enviroment.
> there was also a free ware dll that allowed sql to invoke the ras dialer..
> does anyone have the valid url to this?
Showing posts with label business. Show all posts
Showing posts with label business. Show all posts
Wednesday, March 21, 2012
Replication between 2 SBS (small business server) Trusts
I have SQL running on SBS Server A. It is a publisher and a distributor of a
database that has 1 subscriber a SQL Server running on SBS Server 2. How does
one replicate in a untrusted enviroment.
there was also a free ware dll that allowed sql to invoke the ras dialer..
does anyone have the valid url to this?
Mario,
have a look at this article: http://support.microsoft.com/?id=321822
(HOW TO: Replicate Between Computers Running SQL Server in Non-Trusted
Domains or Across the Internet).
HTH,
Paul Ibison
|||ooops i spoke too soon..
This Q article had only 2 paragraphs that mentioned connection between 2
non-trusted domains. essentially it suggested creating a server agent account
on both machines. it says you 'must set up pass through authentication'.
There is was some data missing from the article.
1) How do you set up 'pass through authentication" via a SQL Agent Account?
2) Assuming 'Pass Through' is enabled, how does one reference the SBS Server?
a) 'Local Area Connection' IP Address (not likely) 192.168.0.2 (private)
b) Local Server Name. MyServer
c) FQDN MyCompany.MyServer.
d) Public Resolvable Domain Name MyCompany.com
i) With extension .com
ii) Without extension
e) Network Connection IP Address of Server 68.XXX.XXX.217 (Public)
None of the above options worked for me, response "Server doesn't exsist or
Access denied" (which is it? MDAC doesn't even know if the Server Exists?
What’s with that?)
I found the information sources lacking. None seemed to illustrate a Point A
to Point Z scenario on SBS. This is not a Version 1 product and being that
trusts are not allowed it's conceivable that many companies would be
attempting non-trusted replication.
PS, I've checked Kbase, SQL BOL, 4 MVP sites, Newsgroups, Online Concierge
and SSWUG. I was exposed to answer bits, in addition to the above mentioned
options, there was mentioned RPC over TCP, RPC over UDP, Linked server
options, Remote server options, SSL options, replication via Backup and
Restore, replication via output files, Replication via terminal services
etc..
Now, I'm a person of reasonable intelligence, willing to the put the time
and effort into research, but am I wrong here when I suggest that the
documentation is all over the map? I will be posting this reply in both the
SQL Connectivity and SQL Replication newsgroups. In my opinion Microsoft does
a great job of documenting the scope and detail of it's technologies but
often falls short when it comes to implementation documentation. They are 2
distinct types of technical writing. I love Microsoft products and take the
time to scribe my opinion in hopes that it will yield stronger product line.
With that said, I ask again for a -concise, thorough, list of steps on how
to set up a push transaction based SQL replication subscription between 2
Non-trusted Small Business Servers?
"Paul Ibison" wrote:
> Mario,
> have a look at this article: http://support.microsoft.com/?id=321822
> (HOW TO: Replicate Between Computers Running SQL Server in Non-Trusted
> Domains or Across the Internet).
> HTH,
> Paul Ibison
>
>
|||Mario,
much of this article applies to your situation, although admittedly it's not
immediately obvious
Remember to set up the alias using the client network utility, rather than
the IP address.
Try using sql server authentication rather than pass-through.
Set up FTP forthe initial snapshot if it isn't a nosync one.
If you want things a little easier, you can use a VPN.
HTH,
Paul Ibison
"Mario Michela" <MarioMichela@.discussions.microsoft.com> wrote in message
news:75DB0BE3-9379-4C57-BC35-3E62104060E7@.microsoft.com...
> ooops i spoke too soon..
> This Q article had only 2 paragraphs that mentioned connection between 2
> non-trusted domains. essentially it suggested creating a server agent
account
> on both machines. it says you 'must set up pass through authentication'.
> There is was some data missing from the article.
> 1) How do you set up 'pass through authentication" via a SQL Agent
Account?
> 2) Assuming 'Pass Through' is enabled, how does one reference the SBS
Server?
> a) 'Local Area Connection' IP Address (not likely) 192.168.0.2
(private)
> b) Local Server Name. MyServer
> c) FQDN MyCompany.MyServer.
> d) Public Resolvable Domain Name MyCompany.com
> i) With extension .com
> ii) Without extension
> e) Network Connection IP Address of Server 68.XXX.XXX.217 (Public)
> None of the above options worked for me, response "Server doesn't exsist
or
> Access denied" (which is it? MDAC doesn't even know if the Server Exists?
> What's with that?)
> I found the information sources lacking. None seemed to illustrate a Point
A
> to Point Z scenario on SBS. This is not a Version 1 product and being that
> trusts are not allowed it's conceivable that many companies would be
> attempting non-trusted replication.
> PS, I've checked Kbase, SQL BOL, 4 MVP sites, Newsgroups, Online Concierge
> and SSWUG. I was exposed to answer bits, in addition to the above
mentioned
> options, there was mentioned RPC over TCP, RPC over UDP, Linked server
> options, Remote server options, SSL options, replication via Backup and
> Restore, replication via output files, Replication via terminal services
> etc..
> Now, I'm a person of reasonable intelligence, willing to the put the time
> and effort into research, but am I wrong here when I suggest that the
> documentation is all over the map? I will be posting this reply in both
the
> SQL Connectivity and SQL Replication newsgroups. In my opinion Microsoft
does
> a great job of documenting the scope and detail of it's technologies but
> often falls short when it comes to implementation documentation. They are
2
> distinct types of technical writing. I love Microsoft products and take
the
> time to scribe my opinion in hopes that it will yield stronger product
line.[vbcol=seagreen]
> With that said, I ask again for a -concise, thorough, list of steps on how
> to set up a push transaction based SQL replication subscription between 2
> Non-trusted Small Business Servers?
>
>
> "Paul Ibison" wrote:
|||Yes the article is good in many respects, i learned a lot, perhaps a bit too
much in that it introduced several differernt approches. ok, now you mention
alaising using the client utility? there are only 3 boxes, can you give me an
example of what to put in them. remember this is a push from the publisher.
so wouldn't the publisher connect to the client server? MS is mixing
mediphores. Am i wrong to assume that data flows from a server (publisher)
using a distributer to a client (subscriber). This can't be that difficult.
currently i have created a domain user (admin rights) on both servers, both
have the same username and password. I"ve also gone into routing/ip
routing/nat/basic firewall and in the public ip address added the following:
Desc of Svc: SQLServer
On public Interface
Using TCP
Incoming Port: 1433
Priv IP:192.168.10.2
OutGoing port: 1433
Desc of Svc: SQLServer UDP
On public Interface
Using UDP
Incoming Port: 1434
Priv IP:192.168.10.2
OutGoing port: 1434
I've been trying to test my creating a UDL. (both servers have an Admin
account, both have the same password -so windows authenticed).
now because the documentation can't seem to use consistant mediphoores. i've
done every on both server in a despirate attempt to shotgun my way into
success (not the best way to go about things but look at what i've got to
work with.)
ok now on to ailases. (again i will build identicle alaises on both machines
untill advised otherwise).
Server Alais: aawwserver (machine/server name)
Server Name: aawwserver
Dynamically Determine port.
is there a wizard or some sort of tool i should be using for this?
i can't believe that this entire process up till this point is covered in a
single paragraph.
At one point I had the whole set up using a vpn (not practicle) but the
transaction agent failed because it couldn't drop a function because it was
being used by replication(funny i never dropped it? why should the
replication agent) so i removed replication and attempted to start from
scratch. I've been at this for aprox 40 hours non-stop not including the 4
days prior. if this is what is concidered a reasonable implimemtation I have
to question the product. So for the sake of my sanity Please Please, provide
an example. using the following 'aliases' (sorry i couldn't resist)
-Example Name-
Publisher:
Machine Name: srvPub
Public IP: 0.0.0.1
Private IP: 0.0.0.2
database: DBPub
Domain: DomPub.com
sql Agent Acct: agtRep
sql Agent Password: agt@.Rep
Subscriber:
Machine Name: srvSub
Public IP: 0.0.0.3
Private IP: 0.0.0.4
database: DBSub
Domain: DomSub.com
sql Agent Acct: agtRep
sql Agent Password: agt@.Rep
The Challange:
Can anyone take the variables I've listed and form them into a coherent set
of instructions.
This has been more stressfull then having to sing the national anthem naked
at the olympics..
Thanks you so very much, for your assistance. .
"Paul Ibison" wrote:
> Mario,
> much of this article applies to your situation, although admittedly it's not
> immediately obvious
> Remember to set up the alias using the client network utility, rather than
> the IP address.
> Try using sql server authentication rather than pass-through.
> Set up FTP forthe initial snapshot if it isn't a nosync one.
> If you want things a little easier, you can use a VPN.
> HTH,
> Paul Ibison
>
> "Mario Michela" <MarioMichela@.discussions.microsoft.com> wrote in message
> news:75DB0BE3-9379-4C57-BC35-3E62104060E7@.microsoft.com...
> account
> Account?
> Server?
> (private)
> or
> A
> mentioned
> the
> does
> 2
> the
> line.
>
>
sql
database that has 1 subscriber a SQL Server running on SBS Server 2. How does
one replicate in a untrusted enviroment.
there was also a free ware dll that allowed sql to invoke the ras dialer..
does anyone have the valid url to this?
Mario,
have a look at this article: http://support.microsoft.com/?id=321822
(HOW TO: Replicate Between Computers Running SQL Server in Non-Trusted
Domains or Across the Internet).
HTH,
Paul Ibison
|||ooops i spoke too soon..
This Q article had only 2 paragraphs that mentioned connection between 2
non-trusted domains. essentially it suggested creating a server agent account
on both machines. it says you 'must set up pass through authentication'.
There is was some data missing from the article.
1) How do you set up 'pass through authentication" via a SQL Agent Account?
2) Assuming 'Pass Through' is enabled, how does one reference the SBS Server?
a) 'Local Area Connection' IP Address (not likely) 192.168.0.2 (private)
b) Local Server Name. MyServer
c) FQDN MyCompany.MyServer.
d) Public Resolvable Domain Name MyCompany.com
i) With extension .com
ii) Without extension
e) Network Connection IP Address of Server 68.XXX.XXX.217 (Public)
None of the above options worked for me, response "Server doesn't exsist or
Access denied" (which is it? MDAC doesn't even know if the Server Exists?
What’s with that?)
I found the information sources lacking. None seemed to illustrate a Point A
to Point Z scenario on SBS. This is not a Version 1 product and being that
trusts are not allowed it's conceivable that many companies would be
attempting non-trusted replication.
PS, I've checked Kbase, SQL BOL, 4 MVP sites, Newsgroups, Online Concierge
and SSWUG. I was exposed to answer bits, in addition to the above mentioned
options, there was mentioned RPC over TCP, RPC over UDP, Linked server
options, Remote server options, SSL options, replication via Backup and
Restore, replication via output files, Replication via terminal services
etc..
Now, I'm a person of reasonable intelligence, willing to the put the time
and effort into research, but am I wrong here when I suggest that the
documentation is all over the map? I will be posting this reply in both the
SQL Connectivity and SQL Replication newsgroups. In my opinion Microsoft does
a great job of documenting the scope and detail of it's technologies but
often falls short when it comes to implementation documentation. They are 2
distinct types of technical writing. I love Microsoft products and take the
time to scribe my opinion in hopes that it will yield stronger product line.
With that said, I ask again for a -concise, thorough, list of steps on how
to set up a push transaction based SQL replication subscription between 2
Non-trusted Small Business Servers?
"Paul Ibison" wrote:
> Mario,
> have a look at this article: http://support.microsoft.com/?id=321822
> (HOW TO: Replicate Between Computers Running SQL Server in Non-Trusted
> Domains or Across the Internet).
> HTH,
> Paul Ibison
>
>
|||Mario,
much of this article applies to your situation, although admittedly it's not
immediately obvious
Remember to set up the alias using the client network utility, rather than
the IP address.
Try using sql server authentication rather than pass-through.
Set up FTP forthe initial snapshot if it isn't a nosync one.
If you want things a little easier, you can use a VPN.
HTH,
Paul Ibison
"Mario Michela" <MarioMichela@.discussions.microsoft.com> wrote in message
news:75DB0BE3-9379-4C57-BC35-3E62104060E7@.microsoft.com...
> ooops i spoke too soon..
> This Q article had only 2 paragraphs that mentioned connection between 2
> non-trusted domains. essentially it suggested creating a server agent
account
> on both machines. it says you 'must set up pass through authentication'.
> There is was some data missing from the article.
> 1) How do you set up 'pass through authentication" via a SQL Agent
Account?
> 2) Assuming 'Pass Through' is enabled, how does one reference the SBS
Server?
> a) 'Local Area Connection' IP Address (not likely) 192.168.0.2
(private)
> b) Local Server Name. MyServer
> c) FQDN MyCompany.MyServer.
> d) Public Resolvable Domain Name MyCompany.com
> i) With extension .com
> ii) Without extension
> e) Network Connection IP Address of Server 68.XXX.XXX.217 (Public)
> None of the above options worked for me, response "Server doesn't exsist
or
> Access denied" (which is it? MDAC doesn't even know if the Server Exists?
> What's with that?)
> I found the information sources lacking. None seemed to illustrate a Point
A
> to Point Z scenario on SBS. This is not a Version 1 product and being that
> trusts are not allowed it's conceivable that many companies would be
> attempting non-trusted replication.
> PS, I've checked Kbase, SQL BOL, 4 MVP sites, Newsgroups, Online Concierge
> and SSWUG. I was exposed to answer bits, in addition to the above
mentioned
> options, there was mentioned RPC over TCP, RPC over UDP, Linked server
> options, Remote server options, SSL options, replication via Backup and
> Restore, replication via output files, Replication via terminal services
> etc..
> Now, I'm a person of reasonable intelligence, willing to the put the time
> and effort into research, but am I wrong here when I suggest that the
> documentation is all over the map? I will be posting this reply in both
the
> SQL Connectivity and SQL Replication newsgroups. In my opinion Microsoft
does
> a great job of documenting the scope and detail of it's technologies but
> often falls short when it comes to implementation documentation. They are
2
> distinct types of technical writing. I love Microsoft products and take
the
> time to scribe my opinion in hopes that it will yield stronger product
line.[vbcol=seagreen]
> With that said, I ask again for a -concise, thorough, list of steps on how
> to set up a push transaction based SQL replication subscription between 2
> Non-trusted Small Business Servers?
>
>
> "Paul Ibison" wrote:
|||Yes the article is good in many respects, i learned a lot, perhaps a bit too
much in that it introduced several differernt approches. ok, now you mention
alaising using the client utility? there are only 3 boxes, can you give me an
example of what to put in them. remember this is a push from the publisher.
so wouldn't the publisher connect to the client server? MS is mixing
mediphores. Am i wrong to assume that data flows from a server (publisher)
using a distributer to a client (subscriber). This can't be that difficult.
currently i have created a domain user (admin rights) on both servers, both
have the same username and password. I"ve also gone into routing/ip
routing/nat/basic firewall and in the public ip address added the following:
Desc of Svc: SQLServer
On public Interface
Using TCP
Incoming Port: 1433
Priv IP:192.168.10.2
OutGoing port: 1433
Desc of Svc: SQLServer UDP
On public Interface
Using UDP
Incoming Port: 1434
Priv IP:192.168.10.2
OutGoing port: 1434
I've been trying to test my creating a UDL. (both servers have an Admin
account, both have the same password -so windows authenticed).
now because the documentation can't seem to use consistant mediphoores. i've
done every on both server in a despirate attempt to shotgun my way into
success (not the best way to go about things but look at what i've got to
work with.)
ok now on to ailases. (again i will build identicle alaises on both machines
untill advised otherwise).
Server Alais: aawwserver (machine/server name)
Server Name: aawwserver
Dynamically Determine port.
is there a wizard or some sort of tool i should be using for this?
i can't believe that this entire process up till this point is covered in a
single paragraph.
At one point I had the whole set up using a vpn (not practicle) but the
transaction agent failed because it couldn't drop a function because it was
being used by replication(funny i never dropped it? why should the
replication agent) so i removed replication and attempted to start from
scratch. I've been at this for aprox 40 hours non-stop not including the 4
days prior. if this is what is concidered a reasonable implimemtation I have
to question the product. So for the sake of my sanity Please Please, provide
an example. using the following 'aliases' (sorry i couldn't resist)
-Example Name-
Publisher:
Machine Name: srvPub
Public IP: 0.0.0.1
Private IP: 0.0.0.2
database: DBPub
Domain: DomPub.com
sql Agent Acct: agtRep
sql Agent Password: agt@.Rep
Subscriber:
Machine Name: srvSub
Public IP: 0.0.0.3
Private IP: 0.0.0.4
database: DBSub
Domain: DomSub.com
sql Agent Acct: agtRep
sql Agent Password: agt@.Rep
The Challange:
Can anyone take the variables I've listed and form them into a coherent set
of instructions.
This has been more stressfull then having to sing the national anthem naked
at the olympics..
Thanks you so very much, for your assistance. .
"Paul Ibison" wrote:
> Mario,
> much of this article applies to your situation, although admittedly it's not
> immediately obvious
> Remember to set up the alias using the client network utility, rather than
> the IP address.
> Try using sql server authentication rather than pass-through.
> Set up FTP forthe initial snapshot if it isn't a nosync one.
> If you want things a little easier, you can use a VPN.
> HTH,
> Paul Ibison
>
> "Mario Michela" <MarioMichela@.discussions.microsoft.com> wrote in message
> news:75DB0BE3-9379-4C57-BC35-3E62104060E7@.microsoft.com...
> account
> Account?
> Server?
> (private)
> or
> A
> mentioned
> the
> does
> 2
> the
> line.
>
>
sql
Replication between 2 SBS (small business server) Trusts
I have SQL running on SBS Server A. It is a publisher and a distributor of a
database that has 1 subscriber a SQL Server running on SBS Server 2. How doe
s
one replicate in a untrusted enviroment.
there was also a free ware dll that allowed sql to invoke the ras dialer..
does anyone have the valid url to this?-- Current Standings (taken from my post on the SBS Site) --
I posted on the SQL server site and was referred to Q321822. This Q article
had only 2 paragraphs that mentioned connection between 2 non-trusted
domains. essentially it suggested creating a server agent account on both
machines. it says you 'must set up pass through authentication'. There is wa
s
some data missing from the article.
1) How do you set up 'pass through authentication" via a SQL Agent Account?
2) Assuming 'Pass Through' is enabled, how does one reference the SBS Server
?
a) 'Local Area Connection' IP Address (not likely) 192.168.0.2 (private)
b) Local Server Name. MyServer
c) FQDN MyCompany.MyServer.
d) Public Resolvable Domain Name MyCompany.com
i) With extension .com
ii) Without extension
e) Network Connection IP Address of Server 68.XXX.XXX.217 (Public)
None of the above options worked for me, response "Server doesn't exsist or
Access denied" (which is it? MDAC doesn't even know if the Server Exists?
What’s with that?)
I found the information sources lacking. None seemed to illustrate a Point A
to Point Z scenario on SBS. This is not a Version 1 product and being that
trusts are not allowed it's conceivable that many companies would be
attempting non-trusted replication.
PS, I've checked Kbase, SQL BOL, 4 MVP sites, Newsgroups, Online Concierge
and SSWUG. I was exposed to answer bits, in addition to the above mentioned
options, there was mentioned RPC over TCP, RPC over UDP, Linked server
options, Remote server options, SSL options, replication via Backup and
Restore, replication via output files, Replication via terminal services
etc..
Now, I'm a person of reasonable intelligence, willing to the put the time
and effort into research, but am I wrong here when I suggest that the
documentation is all over the map? I will be posting this reply in both the
SQL Connectivity and SQL Replication newsgroups. In my opinion Microsoft doe
s
a great job of documenting the scope and detail of it's technologies but
often falls short when it comes to implementation documentation. They are 2
distinct types of technical writing. I love Microsoft products and take the
time to scribe my opinion in hopes that it will yield stronger product line.
With that said, I ask again for a -concise, thorough, list of steps on how
to set up a push transaction based SQL replication subscription between 2
Non-trusted Small Business Servers?
"Mario Michela" wrote:
> I have SQL running on SBS Server A. It is a publisher and a distributor of
a
> database that has 1 subscriber a SQL Server running on SBS Server 2. How d
oes
> one replicate in a untrusted enviroment.
> there was also a free ware dll that allowed sql to invoke the ras dialer..
> does anyone have the valid url to this?
database that has 1 subscriber a SQL Server running on SBS Server 2. How doe
s
one replicate in a untrusted enviroment.
there was also a free ware dll that allowed sql to invoke the ras dialer..
does anyone have the valid url to this?-- Current Standings (taken from my post on the SBS Site) --
I posted on the SQL server site and was referred to Q321822. This Q article
had only 2 paragraphs that mentioned connection between 2 non-trusted
domains. essentially it suggested creating a server agent account on both
machines. it says you 'must set up pass through authentication'. There is wa
s
some data missing from the article.
1) How do you set up 'pass through authentication" via a SQL Agent Account?
2) Assuming 'Pass Through' is enabled, how does one reference the SBS Server
?
a) 'Local Area Connection' IP Address (not likely) 192.168.0.2 (private)
b) Local Server Name. MyServer
c) FQDN MyCompany.MyServer.
d) Public Resolvable Domain Name MyCompany.com
i) With extension .com
ii) Without extension
e) Network Connection IP Address of Server 68.XXX.XXX.217 (Public)
None of the above options worked for me, response "Server doesn't exsist or
Access denied" (which is it? MDAC doesn't even know if the Server Exists?
What’s with that?)
I found the information sources lacking. None seemed to illustrate a Point A
to Point Z scenario on SBS. This is not a Version 1 product and being that
trusts are not allowed it's conceivable that many companies would be
attempting non-trusted replication.
PS, I've checked Kbase, SQL BOL, 4 MVP sites, Newsgroups, Online Concierge
and SSWUG. I was exposed to answer bits, in addition to the above mentioned
options, there was mentioned RPC over TCP, RPC over UDP, Linked server
options, Remote server options, SSL options, replication via Backup and
Restore, replication via output files, Replication via terminal services
etc..
Now, I'm a person of reasonable intelligence, willing to the put the time
and effort into research, but am I wrong here when I suggest that the
documentation is all over the map? I will be posting this reply in both the
SQL Connectivity and SQL Replication newsgroups. In my opinion Microsoft doe
s
a great job of documenting the scope and detail of it's technologies but
often falls short when it comes to implementation documentation. They are 2
distinct types of technical writing. I love Microsoft products and take the
time to scribe my opinion in hopes that it will yield stronger product line.
With that said, I ask again for a -concise, thorough, list of steps on how
to set up a push transaction based SQL replication subscription between 2
Non-trusted Small Business Servers?
"Mario Michela" wrote:
> I have SQL running on SBS Server A. It is a publisher and a distributor of
a
> database that has 1 subscriber a SQL Server running on SBS Server 2. How d
oes
> one replicate in a untrusted enviroment.
> there was also a free ware dll that allowed sql to invoke the ras dialer..
> does anyone have the valid url to this?
Replication Architecture: Design Issue and Validation
I would like some validation on a replication architecture.
Business Context:
We are deploying a custom .NET 2 application for an retail/distribution
operation with 10 locations. The remote locations must have the ability to
continue to operate even if the central site is unavailable (these are mostly
rural locations).
Replication Requirements:
1. Corporate objects must be available to the remote locations as soon as
possible (e.g., purchase orders so that remote can receive against PO and
match line items).
2. Remote objects must be available to the corporate office and then made
available to the other remote locations as soon as possible (e.g., inventory
transfer "out").
3. All objects will be periodically processed by corporate with objects
produced via process sent to the remote locations (e.g., inventory count
checkpoints).
4. As much as possible the model should allow for a) schema changes given
that this is a v1; and b) minimal maintenance given that of 5 I.T. staff only
1 is a DBA.
Replication Architecture
A Corporate Objects shall be published to remote locations with a merge push
subscription
B Remote location Objects shall be published to the corporate office with a
merge pull subscription and then re-published to the other remote locations
via a push merge
I have a reasonable amount of SQL experience but am new to replication. I
am looking for the following feedback: a) does this design meet the business
context and application requirements; b) how do I make sure that the remote
location transactions which come in to corporate go out to the other
locations.
Thanks
Philip Neufeld, MCSE
I think you can get away with a single merge publication. If your remote
locations are well connected use push. What will happen is if branch 1 makes
a change it will go to the central location and from there be sent to all
other branches who need that copy. You can filter the data using horizontal
partitioning or row filters if you need to.
If you are using SQL 2005 schema changes can be replicated from the central
office to the branch offices.
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
"Philip Neufeld" <PhilipNeufeld@.discussions.microsoft.com> wrote in message
news:D255F0EE-E958-4350-937F-4562AABA3C5C@.microsoft.com...
>I would like some validation on a replication architecture.
> Business Context:
> We are deploying a custom .NET 2 application for an retail/distribution
> operation with 10 locations. The remote locations must have the ability
> to
> continue to operate even if the central site is unavailable (these are
> mostly
> rural locations).
> Replication Requirements:
> 1. Corporate objects must be available to the remote locations as soon as
> possible (e.g., purchase orders so that remote can receive against PO and
> match line items).
> 2. Remote objects must be available to the corporate office and then made
> available to the other remote locations as soon as possible (e.g.,
> inventory
> transfer "out").
> 3. All objects will be periodically processed by corporate with objects
> produced via process sent to the remote locations (e.g., inventory count
> checkpoints).
> 4. As much as possible the model should allow for a) schema changes given
> that this is a v1; and b) minimal maintenance given that of 5 I.T. staff
> only
> 1 is a DBA.
> Replication Architecture
> A Corporate Objects shall be published to remote locations with a merge
> push
> subscription
> B Remote location Objects shall be published to the corporate office with
> a
> merge pull subscription and then re-published to the other remote
> locations
> via a push merge
> I have a reasonable amount of SQL experience but am new to replication. I
> am looking for the following feedback: a) does this design meet the
> business
> context and application requirements; b) how do I make sure that the
> remote
> location transactions which come in to corporate go out to the other
> locations.
> Thanks
> Philip Neufeld, MCSE
Business Context:
We are deploying a custom .NET 2 application for an retail/distribution
operation with 10 locations. The remote locations must have the ability to
continue to operate even if the central site is unavailable (these are mostly
rural locations).
Replication Requirements:
1. Corporate objects must be available to the remote locations as soon as
possible (e.g., purchase orders so that remote can receive against PO and
match line items).
2. Remote objects must be available to the corporate office and then made
available to the other remote locations as soon as possible (e.g., inventory
transfer "out").
3. All objects will be periodically processed by corporate with objects
produced via process sent to the remote locations (e.g., inventory count
checkpoints).
4. As much as possible the model should allow for a) schema changes given
that this is a v1; and b) minimal maintenance given that of 5 I.T. staff only
1 is a DBA.
Replication Architecture
A Corporate Objects shall be published to remote locations with a merge push
subscription
B Remote location Objects shall be published to the corporate office with a
merge pull subscription and then re-published to the other remote locations
via a push merge
I have a reasonable amount of SQL experience but am new to replication. I
am looking for the following feedback: a) does this design meet the business
context and application requirements; b) how do I make sure that the remote
location transactions which come in to corporate go out to the other
locations.
Thanks
Philip Neufeld, MCSE
I think you can get away with a single merge publication. If your remote
locations are well connected use push. What will happen is if branch 1 makes
a change it will go to the central location and from there be sent to all
other branches who need that copy. You can filter the data using horizontal
partitioning or row filters if you need to.
If you are using SQL 2005 schema changes can be replicated from the central
office to the branch offices.
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
"Philip Neufeld" <PhilipNeufeld@.discussions.microsoft.com> wrote in message
news:D255F0EE-E958-4350-937F-4562AABA3C5C@.microsoft.com...
>I would like some validation on a replication architecture.
> Business Context:
> We are deploying a custom .NET 2 application for an retail/distribution
> operation with 10 locations. The remote locations must have the ability
> to
> continue to operate even if the central site is unavailable (these are
> mostly
> rural locations).
> Replication Requirements:
> 1. Corporate objects must be available to the remote locations as soon as
> possible (e.g., purchase orders so that remote can receive against PO and
> match line items).
> 2. Remote objects must be available to the corporate office and then made
> available to the other remote locations as soon as possible (e.g.,
> inventory
> transfer "out").
> 3. All objects will be periodically processed by corporate with objects
> produced via process sent to the remote locations (e.g., inventory count
> checkpoints).
> 4. As much as possible the model should allow for a) schema changes given
> that this is a v1; and b) minimal maintenance given that of 5 I.T. staff
> only
> 1 is a DBA.
> Replication Architecture
> A Corporate Objects shall be published to remote locations with a merge
> push
> subscription
> B Remote location Objects shall be published to the corporate office with
> a
> merge pull subscription and then re-published to the other remote
> locations
> via a push merge
> I have a reasonable amount of SQL experience but am new to replication. I
> am looking for the following feedback: a) does this design meet the
> business
> context and application requirements; b) how do I make sure that the
> remote
> location transactions which come in to corporate go out to the other
> locations.
> Thanks
> Philip Neufeld, MCSE
Monday, February 20, 2012
Replicating Sql Server to Express Edition as backup application
Hello!
We are running a business critical client-server application that needs to have high availability to the end user.
I was wondering if it would be possible to setup a replication/data transfer from an existing Sql Server 7.0/8.0/9.0 (regular online environment running on server) TO an instance of Sql 2005 Express Edition (backup env. running on klient PC).
In case of server failure the application would redirect - accessing the local PC Express edition.
Does anyone have any input on this, and if it would be a possible alternative to use as extra standby- system. ?
Kind regards
TomasYes this is possible but there are certain exceptions.
And it depends on what kind of replication technology you are looking at.
SQL Server 2005 Books Online has more information on supported topologies.
Search for "Using Multiple Versions of SQL Server in a Replication Topology"|||
Hi Tomas.
It would appear that I have a similar type of need. See this post http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=677662&SiteID=1 which describes my situation. If you've got any further info on how this is achieved please respond. I'll do the same. We were able to create the windows form app and use Sql2005 Std to maintain a 'gold' standard db on our publisher/distributor machine. We have to replace our db daily with an entirely new dataset that is sent to us via a foreign host. We take that data an bulk copy it into our db. Then, we setup a snapshot replication scenario, installing SqlExpress w/ Advance Tools on the subscriber machine.
We install our offline viewer windows smart client application on the subscriber, and are able to bring in a view of the needed data. However, we need this view to be available offline, for use when the prefferred application is unavailable or when the network is down. At this point, if the network is down our replicated db is not available either. So, I'm lost with the way I've got it working now. I'm not sure if it is a setup issue or if I've misunderstood how replication works. At any rate, our need appears to be similar in scope to yours. I'll check back here, and on my post to update the status.
Right now, we are examining our setup of the replication subscription and whether there is a way to achieve the goal desired, or if we have to employ a bulk copy insert into a local database for our subscriber downtime usage.
|||Hi,
You might want to talk to us about a product that we sell (WANSync) which provides real-time asynchronous data replication, full tree replication topologies to protect from server and site failures. Should an SQL database server fail for any reason, a geographically remote SQL replica takes it's place and will allow you to keep working.
If you want more information or want to trial this solution for free, please email me at paul.maziere@.dataplex-systems.com
Regards, Paul.
Replicating Sql Server to Express Edition as backup application
Hello!
We are running a business critical client-server application that needs to have high availability to the end user.
I was wondering if it would be possible to setup a replication/data transfer from an existing Sql Server 7.0/8.0/9.0 (regular online environment running on server) TO an instance of Sql 2005 Express Edition (backup env. running on klient PC).
In case of server failure the application would redirect - accessing the local PC Express edition.
Does anyone have any input on this, and if it would be a possible alternative to use as extra standby- system. ?
Kind regards
TomasYes this is possible but there are certain exceptions.
And it depends on what kind of replication technology you are looking at.
SQL Server 2005 Books Online has more information on supported topologies.
Search for "Using Multiple Versions of SQL Server in a Replication Topology"|||
Hi Tomas.
It would appear that I have a similar type of need. See this post http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=677662&SiteID=1 which describes my situation. If you've got any further info on how this is achieved please respond. I'll do the same. We were able to create the windows form app and use Sql2005 Std to maintain a 'gold' standard db on our publisher/distributor machine. We have to replace our db daily with an entirely new dataset that is sent to us via a foreign host. We take that data an bulk copy it into our db. Then, we setup a snapshot replication scenario, installing SqlExpress w/ Advance Tools on the subscriber machine.
We install our offline viewer windows smart client application on the subscriber, and are able to bring in a view of the needed data. However, we need this view to be available offline, for use when the prefferred application is unavailable or when the network is down. At this point, if the network is down our replicated db is not available either. So, I'm lost with the way I've got it working now. I'm not sure if it is a setup issue or if I've misunderstood how replication works. At any rate, our need appears to be similar in scope to yours. I'll check back here, and on my post to update the status.
Right now, we are examining our setup of the replication subscription and whether there is a way to achieve the goal desired, or if we have to employ a bulk copy insert into a local database for our subscriber downtime usage.
|||Hi,
You might want to talk to us about a product that we sell (WANSync) which provides real-time asynchronous data replication, full tree replication topologies to protect from server and site failures. Should an SQL database server fail for any reason, a geographically remote SQL replica takes it's place and will allow you to keep working.
If you want more information or want to trial this solution for free, please email me at paul.maziere@.dataplex-systems.com
Regards, Paul.
Subscribe to:
Posts (Atom)