The very easiest way to copy a SQL Anywhere database is to do this:
(1) Stop the engine normally. By "normally" I mean shut down the
dbeng10.exe or dbsrv10.exe task, not pull the power cord out of the
computer. During a normal shutdown, the engine will perform a final
checkpoint to ensure the *.db file is up to date, and the *.log file
is not required for a later startup (it will be recreated if it is
missing).
(2) Copy the *.db file to the other location. This other location can
be on a different computer, different operating system, different
"endian" chip architecture... physical SQL Anywhere database files are
binary compatible across Linux, Mac, Windows, Windows Mobile, Unix,
etc.
(3) Start a dbeng10.exe or dbsrv10.exe task using the copied *.db
file.
Generally, every administrative task is easier with SQL Anywhere than
with any other DBMS... especially MySQL... but that's my bias showing.
FWIW there are many other ways to copy data. I'm not sure this way is
what you want, but I'm also not sure how your canned app works with
SQL Anywhere.
Feel free to ask more questions.
Breck
On Mon, 25 Jan 2010 20:04:09 -0800 (PST), Bomee Jung
<bomeejung (AT) gmail (DOT) com> wrote:
Quote:
I have a little situation where we need to have two installations of a
canned app (that runs on sql anywhere 10) and the two installations
can't talk to each other because they're behind firewalls. We need
only one installation to have write/edit ability, but need to have a
full read-only version at the other site.
I assume there is a way to slurp in the whole shebang periodically
(doing a sql dump at the rw site and importing it in at the ro site?)
but is that likely to screw up anything? will it maintain the user
account / password info? If we create a read only account at the full-
access site, will that account info be preserved and usable at the
second site?
Is there any better way to do this, given our counterparty (at the
read-write site) is unable to give us direct access?
Pretty familiar with MySQL and the like, but am worried about what may
get screwed up in the backup and transfer process.
Any help much appreciated!! |
--
Breck Carter - Blog: http://sqlanywhere.blogspot.com/
SQLA questions and answers: http://sqla.stackexchange.com
RisingRoad helps SQL Anywhere developers make better databases
http://www.risingroad.com/
Breck.Carter at gmail