SQL Anywhere database replication

Author

SQL Remote setup

David Kerber

2005-07-27, 11:24 am

I've found the sections in the OLH which describe the various
replication/synchronization methods, and have decided that SQL Remote is
most appropriate for my needs. What I can't find, however, is
instructions on how to set up replication from scratch for existing
databases. Is there a step-by-step or a tutorial somewhere that I'm
missing?

--
Remove the ns_ from if replying by e-mail (but keep posts in the
newsgroups if possible).

Rob Waywell

2005-07-27, 1:24 pm

You said "from scratch" and "for existing databases". From this I'm guessing
that you have a set of existing databases that you would like to start
consolidating at a central location, is that correct?

--
-----------------------------------------------
Robert Waywell
Sybase Adaptive Server Anywhere Developer - Version 8
Sybase Certified Professional

Sybase's iAnywhere Solutions

Please respond ONLY to newsgroup

EBF's and Patches: http://downloads.sybase.com
choose SQL Anywhere Studio >> change 'time frame' to all

To Submit Bug Reports:
http://case-express.sybase.com/cx/c...sc?CASETYPE=Bug

SQL Anywhere Studio Supported Platforms and Support Status
http://my.sybase.com/detail?id=1002288

Whitepapers, TechDocs, and bug fixes are all available through the iAnywhere
Developer Community at www.ianywhere.com/developer
"David Kerber" < ns_dkerber@ns_wraenv
iro.com> wrote in message
news:MPG. 1d5185f2da168d429897
7b@forums.sybase.com...
> I've found the sections in the OLH which describe the various
> replication/synchronization methods, and have decided that SQL Remote is
> most appropriate for my needs. What I can't find, however, is
> instructions on how to set up replication from scratch for existing
> databases. Is there a step-by-step or a tutorial somewhere that I'm
> missing?
>
>
> --
> Remove the ns_ from if replying by e-mail (but keep posts in the
> newsgroups if possible).

David Kerber

2005-07-27, 1:24 pm

In article <42e7cda6@forums-1-dub>, rwaywell@no_spam.ianywhere.com
says...
> You said "from scratch" and "for existing databases". From this I'm guessing
> that you have a set of existing databases that you would like to start
> consolidating at a central location, is that correct?

Yes, exactly (two of them).

--
Remove the ns_ from if replying by e-mail (but keep posts in the
newsgroups if possible).

Rob Waywell

2005-07-28, 8:23 pm

So step one will be for you to build your consolidated database as the
combined set of data from both existing databases. Have you decided how you
will reconcile duplicate key values from the existing data and handle
primary key generation for new data?

--
-----------------------------------------------
Robert Waywell
Sybase Adaptive Server Anywhere Developer - Version 8
Sybase Certified Professional

Sybase's iAnywhere Solutions

Please respond ONLY to newsgroup

EBF's and Patches: http://downloads.sybase.com
choose SQL Anywhere Studio >> change 'time frame' to all

To Submit Bug Reports:
http://case-express.sybase.com/cx/c...sc?CASETYPE=Bug

SQL Anywhere Studio Supported Platforms and Support Status
http://my.sybase.com/detail?id=1002288

Whitepapers, TechDocs, and bug fixes are all available through the iAnywhere
Developer Community at www.ianywhere.com/developer
"David Kerber" < ns_dkerber@ns_wraenv
iro.com> wrote in message
news:MPG. 1d5198cec913b3fd9897
7c@forums.sybase.com...
> In article <42e7cda6@forums-1-dub>, rwaywell@no_spam.ianywhere.com
> says...
>
> Yes, exactly (two of them).
>
> --
> Remove the ns_ from if replying by e-mail (but keep posts in the
> newsgroups if possible).

David Kerber

2005-07-28, 8:23 pm

In article <42e92dc5$1@forums-1-dub>, rwaywell@no_spam.ianywhere.com
says...
> So step one will be for you to build your consolidated database as the
> combined set of data from both existing databases. Have you decided how you
> will reconcile duplicate key values from the existing data and handle
> primary key generation for new data?

At the moment one of them is simply an older version of the other (disk
copy of .db file), so there will be no conflicts in the pKeys for now.
I just can't see anything about what I need to do to get replication
started. It's actually really more of a synchronization job than
replication, but I can tolerate a few-to-several minute delay between
them.

--
Remove the ns_ from if replying by e-mail (but keep posts in the
newsgroups if possible).

Reg Domaratzki $iAnywhere Solutions$

2005-07-29, 9:23 am

Am I to understand from you last post that the older version of the database
has not been modified since the copy was taken, and that the "current"
version of the database contains additional data, but there is no data in
the older version of the database that does not exist in the new version?

If so, then we can scrap the "old" database, so it makes things much easier.
Here's the general outline of the steps you'd take :

1) Define your publication in the "current" database, which will become your
consolidated database.
2) Create a Publisher for the consolidated database, and define the address
for the consolidated user using the CREATE REMOTE MESSAGE TYPE command.
3) Create your remote users and subscribe them to the publication.
4) Extract your remote users. I'd use dbxtract for your first attempt, but
you'll quickly find that there are much better ways to extract your remotes.
5) Setup your messaging system (i.e. define directories for FILE/FTP, add
e-mail users, ... )
6) Start running dbremote.

The steps you take are going to very similar to those in the Tutorial. The
tutorial sets up replication on the asademo database, which is already
populated with data, just like your database.

SQL Remote User's Guide
Tutorials for Adaptive Server Anywhere Users
Tutorial: Adaptive Server Anywhere replication using Interactive SQL and
dbxtract

Of course, the main difference for you is that your table names will be
different when defining your publication.

As Rob pointed out, the tricky part to getting this started is if you need
to consolidated the data in two distinct databases into one database,
particularly when the two distinct databases have likely been using the same
primary key values up to now.

--
Reg Domaratzki, Sybase iAnywhere Solutions
Sybase Certified Professional - Sybase ASA Developer Version 8
Please reply only to the newsgroup

iAnywhere Developer Community : http://www.ianywhere.com/developer
iAnywhere Documentation : http://www.ianywhere.com/developer/product_manuals
ASA Patches and EBFs : http://downloads.sybase.com/swx/sdmain.stm
-> Choose SQL Anywhere Studio
-> Set "Platform Preview" and "Time Frame" to ALL

"David Kerber" < ns_dkerber@ns_wraenv
iro.com> wrote in message
news:MPG. 1d5307526a701f529897
7d@forums.sybase.com...
> In article <42e92dc5$1@forums-1-dub>, rwaywell@no_spam.ianywhere.com
> says...
you[color=darkred]
>
> At the moment one of them is simply an older version of the other (disk
> copy of .db file), so there will be no conflicts in the pKeys for now.
> I just can't see anything about what I need to do to get replication
> started. It's actually really more of a synchronization job than
> replication, but I can tolerate a few-to-several minute delay between
> them.
>
> --
> Remove the ns_ from if replying by e-mail (but keep posts in the
> newsgroups if possible).

David Kerber

2005-07-29, 11:24 am

In article <42ea3abd$1@forums-1-dub>, FirstName.LastName@ianywhere.com
says...
> Am I to understand from you last post that the older version of the database
> has not been modified since the copy was taken, and that the "current"
> version of the database contains additional data, but there is no data in
> the older version of the database that does not exist in the new version?

Yes, that is correct.

> If so, then we can scrap the "old" database, so it makes things much easier.
> Here's the general outline of the steps you'd take :

That's just what I was looking for, but apparently didn't see the
tutorial when I was searching the other day. I'll give it a go...

....

Thanks!
--
Remove the ns_ from if replying by e-mail (but keep posts in the
newsgroups if possible).

Sponsored Links