SQL Anywhere Mobile

Author

Extract

Suri Goura

2005-03-30, 9:42 am

Hi

I am exploring Mobilink, we are on DBRemote..

Is there a equivalent to database extraction for remote users ?

thanks
Suri

Greg Fenton

2005-03-30, 9:42 am

Suri Goura wrote:
>
> I am exploring Mobilink, we are on DBRemote..
>
> Is there a equivalent to database extraction for remote users ?
>

There is a dbmlxtract utility that is similar to dbxtract. However, we
suggest that the ML extract utility is not the appropriate tool for most
scenarios.

In our team we typically build a remote database using normal database
methods, that usually being a simple shell script and a .SQL file or two:

dbinit my_new_remote.db
dbisql -c "dsn=my_new_odbc" schema.sql
dbisql -c "dsn=my_new_odbc" initial_data.sql
dbisql -c "dsn=my_new_odbc" add_publicationns.sql

Then you ship the new database file to the remote (or perform the above
steps *at* the remote).

Once you've done that, you simply create the SYNCHRONIZATION USER and
SYNCHRONIZATION SUBSCRIPTION (which are remote-specific).

Hope this helps,
greg.fenton
--
Greg Fenton
Consultant, Solution Services, iAnywhere Solutions
--------
Visit the iAnywhere Solutions Developer Community
Whitepapers, TechDocs, Downloads
http://www.ianywhere.com/developer/

Suri Goura

2005-03-30, 9:42 am

Thanks, Greg. That was helpful. I am just trying to run a sample scenario.
"Greg Fenton" <greg. fenton_NOSPAM_@ianyw
here.com> wrote in message
news:4223840b$1@foru
ms-2-dub...
> Suri Goura wrote:
>
> There is a dbmlxtract utility that is similar to dbxtract. However, we
> suggest that the ML extract utility is not the appropriate tool for most
> scenarios.
>
> In our team we typically build a remote database using normal database
> methods, that usually being a simple shell script and a .SQL file or two:
>
> dbinit my_new_remote.db
> dbisql -c "dsn=my_new_odbc" schema.sql
> dbisql -c "dsn=my_new_odbc" initial_data.sql
> dbisql -c "dsn=my_new_odbc" add_publicationns.sql
>
> Then you ship the new database file to the remote (or perform the above
> steps *at* the remote).
>
> Once you've done that, you simply create the SYNCHRONIZATION USER and
> SYNCHRONIZATION SUBSCRIPTION (which are remote-specific).
>
> Hope this helps,
> greg.fenton
> --
> Greg Fenton
> Consultant, Solution Services, iAnywhere Solutions
> --------
> Visit the iAnywhere Solutions Developer Community
> Whitepapers, TechDocs, Downloads
> http://www.ianywhere.com/developer/

Sponsored Links