Zumero


Zumero for SQL Server v2.2 - Release Notes

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

New features in ZSS 2.2

  • You can now choose to purge server-side historical data on a per-table basis. On its own, ZSS kept old historical “housekeeping” data permanently, so that any client could efficiently “catch up” to the server no matter how long it had been since the last sync. SQL Server storage could grow significanly as a result. Now, you can remove data that is too old — or falls outside of a sync filter — with predictable results when older clients re-sync. See the documentation for details, options, and side-effects.
  • ZSS now has options for handling Foreign Key Constraint violations on sync — e.g. when a “parent” row is deleted on one client and a “child” row (referencing that parent) is added on another client; or when the parent row is deleted on one client and a child is modified on another client.

Improvements and fixes in ZSS 2.2

  • ZSS Manager and Server now handle custom user tables consistently - whether the user table is in a non-Zumero schema, named something other than “users”, or actually a View instead of a Table.
  • The Xamarin Android library now supports 64-bit target architectures.
  • iOS and Mac ZSS clients now provide more progress detail via the sync callback function.
  • Zumero’s housekeeping triggers now pass validation by many SQL Server Integration Services (SSIS) import packages.
  • Stability and performance fixes throughout ZSS Manager and ZSS Server.
  • Improved support for multi-database configurations with SQL Azure.

Note for Mac/iOS app developers

The Mac and iOS libraries now use the NSUrlSession network stack, which — by default — limits web connections to secured (HTTPS) channels. To access insecured (HTTP) servers — e.g. in a development environment where security is not a concern — you’ll need to add NSAllowsArbitraryLoads == true to your app’s Info.plist file. This is usually as simple as including:

<key>NSAppTransportSecurity</key>
<dict>
  <key>NSAllowsArbitraryLoads</key>
  <true/>
</dict>

before the final </dict> tag in Info.plist.

Upgrade Instructions

Upgrading from ZSS 2.x:

  1. Upgrade your ZSS Server. The IIS Zumero web site should be stopped before running the ZSS Server installer.
  2. Upgrade ZSS Manager
  3. Connect to your SQL Server database with ZSS Manager, and follow the upgrade prompts (see Upgrading in the ZSS Manager documentation). If you have multiple databases, you may want to examine them all for upgrades.

Upgrading from ZSS 1.x:

For a walk through of the steps needed to upgrade from ZSS 1.x to 2.2, view our Upgrade Tutorial.

Activation

ZSS Server licenses now require activation. Please visit the Activation page to activate any existing license keys for use with ZSS 2.2.

Upgrade Order

The recommended order for upgrading to ZSS 2.2 is:

  1. Upgrade ZSS Manager
  2. Connect to your SQL Server database with ZSS Manager, and follow the upgrade prompts (see Upgrading in the ZSS Manager documentation). If you have multiple databases, you may want to examine them all for upgrades.
  3. Upgrade your ZSS Server. The IIS Zumero web site should be stopped before running the ZSS Server installer.
  4. Replace the client libraries that you’re using. Rebuild your app and redeploy.

Compatibility

Older clients will work with ZSS 2.2 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.

Release Notes Archive