SQL Anywhere ultralite - publication limit?

Author

publication limit?

Spencer Wasden

2006-01-18, 11:23 am

I'm using 9.0.2.3131 of SQLAnywhere Studio

In Ultralite there is a publication limit of 32. During a sync you could
specify all 32 by setting all bits in the 32 bit bit mask to 1. Is that
more or less correct so far?

I'm wondering... in ASA you can create more than 32 publications. If you
were to use, say, the 1st, 2nd, and 40th ASA publications in an UL db and
try to sync with ASA, would you run into any problems? I don't quite
understand how the UL publication mask is used to reference publications in
ASA. I guess in other words, does the 32 publication limit in UL translate
into a limitation in syncing with ASA? Or are you ok as long as you don't
use more than 32 of the n ASA publications in a UL db?

Thank you.

Michael Thode

2006-01-18, 11:23 am

Your first paragraph is exactly right.

There is no need that UL publications match up with ASA at all when
synchronizing. When you select a publication on the UL client it selects
the tables that are involved in the synchronization. Publications on the
ASA consolidated database aren't used for syncronizating UL. Mobilink
maintains a state information per client based on the publications defined
on the client side not the ASA side. Does that answer your question?

Mike

"Spencer Wasden" <spencer. wasden@mobiledatafor
ce_xspm.com> wrote in message
news:43ce6809$1@foru
ms-1-dub...
> I'm using 9.0.2.3131 of SQLAnywhere Studio
>
> In Ultralite there is a publication limit of 32. During a sync you could
> specify all 32 by setting all bits in the 32 bit bit mask to 1. Is that
> more or less correct so far?
>
> I'm wondering... in ASA you can create more than 32 publications. If you
> were to use, say, the 1st, 2nd, and 40th ASA publications in an UL db and
> try to sync with ASA, would you run into any problems? I don't quite
> understand how the UL publication mask is used to reference publications
in
> ASA. I guess in other words, does the 32 publication limit in UL
translate
> into a limitation in syncing with ASA? Or are you ok as long as you don't
> use more than 32 of the n ASA publications in a UL db?
>
> Thank you.
>
>

Reg Domaratzki $iAnywhere Solutions$

2006-01-18, 11:23 am

Can I ask why you would want to define 32 publication at the remote site?

--
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 filter to "Display ALL platforms IN ALL MONTHS"

"Spencer Wasden" <spencer. wasden@mobiledatafor
ce_xspm.com> wrote in message
news:43ce6809$1@foru
ms-1-dub...
> I'm using 9.0.2.3131 of SQLAnywhere Studio
>
> In Ultralite there is a publication limit of 32. During a sync you could
> specify all 32 by setting all bits in the 32 bit bit mask to 1. Is that
> more or less correct so far?
>
> I'm wondering... in ASA you can create more than 32 publications. If you
> were to use, say, the 1st, 2nd, and 40th ASA publications in an UL db and
> try to sync with ASA, would you run into any problems? I don't quite
> understand how the UL publication mask is used to reference publications
in
> ASA. I guess in other words, does the 32 publication limit in UL
translate
> into a limitation in syncing with ASA? Or are you ok as long as you don't
> use more than 32 of the n ASA publications in a UL db?
>
> Thank you.
>
>

Spencer Wasden

2006-01-18, 1:23 pm

I believe so. Thank you. So theoretically I could have thousands of pubs
on the consolidated but only 32 of those could ever be synced at one time
from UL?

* If * there were a way to dynamically create publications on the client,
then would those be able to sync with ASA as long as the sync scripts
matched?

"Michael Thode" < mthode_no_spam@sybas
e.com> wrote in message
news:43ce6aa2$1@foru
ms-2-dub...
> Your first paragraph is exactly right.
>
> There is no need that UL publications match up with ASA at all when
> synchronizing. When you select a publication on the UL client it selects
> the tables that are involved in the synchronization. Publications on the
> ASA consolidated database aren't used for syncronizating UL. Mobilink
> maintains a state information per client based on the publications defined
> on the client side not the ASA side. Does that answer your question?
>
> Mike
>
>
> "Spencer Wasden" <spencer. wasden@mobiledatafor
ce_xspm.com> wrote in
> message
> news:43ce6809$1@foru
ms-1-dub...
> in
> translate
>
>

Spencer Wasden

2006-01-18, 1:23 pm

At times we want to minimize as much as possible the amount of data that
gets synched over the network. Many pubs would only have 1 or 2 tables.

"Reg Domaratzki (iAnywhere Solutions)" <FirstName.LastName@ianywhere.com>
wrote in message news:43ce715d$1@foru
ms-1-dub...
> Can I ask why you would want to define 32 publication at the remote site?
>
> --
> 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 filter to "Display ALL platforms IN ALL MONTHS"
>
>
> "Spencer Wasden" <spencer. wasden@mobiledatafor
ce_xspm.com> wrote in
> message
> news:43ce6809$1@foru
ms-1-dub...
> in
> translate
>
>

Greg Fenton

2006-01-18, 1:23 pm

Spencer Wasden wrote:
> I believe so. Thank you. So theoretically I could have thousands of pubs
> on the consolidated but only 32 of those could ever be synced at one time
> from UL?

Though it is possible to have multiple publications in UL (and ASA),
with the dozens of apps I have worked with I usually have at most 2
publications. I have once used a grand total of 4 in a remote (and even
there I wanted to use only 3...but the customer insisted).

Also, why would you want to have publications in your consolidated?
Publications are only ever used in a remote to identify the
tables/columns/rows to track changes that get uploaded. The
*consolidated* does not use publications in anyway [well, technically
speaking, the MobiLink *server* does not use publications in the
consolidated in any way...a consolidated could be a remote in a
multi-tired environment, but still the ML *server* would not use the
publication].

> * If * there were a way to dynamically create publications on the client,
> then would those be able to sync with ASA as long as the sync scripts
> matched?

Publications identify the *schema* to be uploaded during a
synchronization. That schema is part of the upload stream sent to the
ML server. It looks something like:

Script Version = MY_VERSION_1

Table MY_FIRST_TABLE, 3 columns:
col1 integer primary key
col2 varchar(200) null
col3 varchar(100) not null
...

MobiLink looks at that schema and now knows that it is to look for
synchronization scripts of version MY_VERSION_1 for the table
MY_FIRST_TABLE and that those scripts will be expecting 3 input
parameters for upload_* events and the download_cursor will provide a
result set with 3 columns in it. [Details of other types of events
omitted for simplicity].

So, again, I wonder why you are thinking about publications at the
consolidated end?

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

Greg Fenton

2006-01-18, 1:23 pm

Spencer Wasden wrote:
> At times we want to minimize as much as possible the amount of data that
> gets synched over the network. Many pubs would only have 1 or 2 tables.
>

Have you done any kind of data analysis to determine how much data you
would be expecting to upload for each of your tables?

From our experience, typically the majority of tables only have a small
number of changes in them. There are often a few key tables that get
the bulk of updates/inserts/deletes, and it is these tables you might
want to move into their own publication(s). Otherwise, you might have
one or two tables you want to frequently synchronize without the
overhead of other tables (e.g. a MESSAGES table), so put that in its own
pub that you synchronize frequently (say, as soon as an outgoing message
is inserted), whereas the other publication that contains all other
tables is synchronized much less frequently (say, once a day).

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/

Spencer Wasden

2006-01-18, 8:23 pm

> Also, why would you want to have publications in your consolidated?

We automate UL publication generation from the consolidated publications
using ulinit. Until a couple months ago we supposed there was a connection
between the two. Anyway, until there's another way of automating UL pub
creation, we will continue to have them in the consolidated.

> *consolidated* does not use publications in anyway [well, technically
> speaking, the MobiLink *server* does not use publications in the
> consolidated in any way...a consolidated could be a remote in a

I have seen a Mobilink log that specifies by name the publication that is
being synchronized. So what I'm seeing must be coming from UL? Here's an
example entry I found in the ML forum:

I. 12/16 01:30:16. Begin synchronizing 'publication1' for MobiLink user
'user1'

Perhaps this isn't UL synching??

"Greg Fenton" <greg. fenton_NOSPAM_@ianyw
here.com> wrote in message
news:43ce8956$1@foru
ms-1-dub...
> Spencer Wasden wrote:
>
> Though it is possible to have multiple publications in UL (and ASA), with
> the dozens of apps I have worked with I usually have at most 2
> publications. I have once used a grand total of 4 in a remote (and even
> there I wanted to use only 3...but the customer insisted).
>
> Also, why would you want to have publications in your consolidated?
> Publications are only ever used in a remote to identify the
> tables/columns/rows to track changes that get uploaded. The
> *consolidated* does not use publications in anyway [well, technically
> speaking, the MobiLink *server* does not use publications in the
> consolidated in any way...a consolidated could be a remote in a
> multi-tired environment, but still the ML *server* would not use the
> publication].
>
>
> Publications identify the *schema* to be uploaded during a
> synchronization. That schema is part of the upload stream sent to the ML
> server. It looks something like:
>
> Script Version = MY_VERSION_1
>
> Table MY_FIRST_TABLE, 3 columns:
> col1 integer primary key
> col2 varchar(200) null
> col3 varchar(100) not null
> ...
>
> MobiLink looks at that schema and now knows that it is to look for
> synchronization scripts of version MY_VERSION_1 for the table
> MY_FIRST_TABLE and that those scripts will be expecting 3 input parameters
> for upload_* events and the download_cursor will provide a result set with
> 3 columns in it. [Details of other types of events omitted for
> simplicity].
>
> So, again, I wonder why you are thinking about publications at the
> consolidated end?
>
> greg.fenton
> --
> Greg Fenton
> Consultant, Solution Services, iAnywhere Solutions
> --------
> Visit the iAnywhere Solutions Developer Community
> Whitepapers, TechDocs, Downloads
> http://www.ianywhere.com/developer/

Greg Fenton

2006-01-18, 8:23 pm

Spencer Wasden wrote:
>
> I. 12/16 01:30:16. Begin synchronizing 'publication1' for MobiLink user
> 'user1'
>
> Perhaps this isn't UL synching??
>

Yes, that is the name of the publication being synchronized, but the ML
server doesn't do anything with it (it might log the name somewhere...).

Recognize that the consolidated database can be Oracle, MSSQL, ASA, ASE
or DB/2. Only 1 of those 5 RDBMSs has a "CREATE PUBLICATION" statement,
so ML does not depend on them at all.

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