Zumero


Zumero for SQL Server v3.1.1 - Release Notes

Zumero for SQL Server (ZSS) v3.1.1 is now available for download in the dev center.

New features and improvements in ZSS 3.1.1:

  • Better error reporting in Android network layer
  • .NET Standard support added to the Zumero NuGet package
  • Added support for SQL Server tables with columns named ROWID, ROWID, or OID (which are reserved names in SQLite)
  • Improved handling of the case where an incoming sync creates a new row with an IDENTITY Primary Key, and the server also needs to apply a new Foreign Key to the client’s database
  • Updated Zumero triggers in SQL Server to handle cases where default values for some connection settings (such as ANSI_PADDING) were set to OFF
  • Added support for columns with a default of (NEWSEQUENTIALID())
  • Improved performance of common sync operations

Bug fixes in ZSS 3.1.1:

  • Fixed error that occurred when a table’s first column is fixed-width and its second column is not
  • Fixed client upgrade error when the server and client were upgraded from 2.3 to 3.x simultaneously

Upgrade Instructions

Upgrade Order

The recommended order for upgrading to ZSS 3.x from 2.x (or older versions) is:

  1. Stop the Zumero web site in IIS.
  2. Upgrade the ZSS Server.
  3. Upgrade the ZSS Manager
  4. Run ZSS Manager and follow the upgrade prompts (see Upgrading in the ZSS Manager documentation). If you have multiple databases, you should examine them all for upgrades.
  5. Restart the IIS site.

Activation

ZSS Server versions 2.x and 3.x require activation. If you are upgrading from version 1.x, please visit the Activation page to activate your existing license keys. If you have already activated your license keys, you do not need to reactivate them or take any additional action for this upgrade.

Compatibility

Older clients will work with ZSS 3.x servers, but will not be able to take full advantage of the new features and improvements. Newer clients will not sync with older ZSS servers.

Clients earlier than ZSS 2.0 should not be used with date-based purging. See the documentation for details.

Release Notes Archive