on 2016 Jul 10 1:01 PM
Hello,
right now, we cannot connect MobiLink to a MS Azure database. mlsrv17 seems to believe it is connecting to a standard MS SQL Server database and tries to retrieve information from system views like dm_os_cluster_nodes which are not present in an Azure database. I know Azure is not on the list of supported consolidated databases but I wonder if someone got it running or wether development has plans to support it?
TIA,
Michael
Request clarification before answering.
For the record: ML seems to support Azure databases starting with build 17.0.7.3903.
At least I just came accross that entry in the readme file of 17.0.8.4003:
================(Build #3903 - Engineering Case #806950)================ The SQLA MobiLink server on Windows now supports SQL server databases running in Microsoft Azure: 1) Setup file: Due to some differences between a regular SQL server and a SQL server running in Microsoft Azure, the MobiLink server setup script file has been modified. Now the SQL server running in Microsoft Azure shares the same MobiLink server setup script file as the regular Microsoft SQL server. The filename of the setup script is syncmss.sql and it can be found under MobiLink\\setup under the SQLA installation. Please only use the one that comes with the SQLA installation image. The setup script file can be applied to a Microsoft Azure SQL server database through the application named Microsoft SQL Server Management Studio; 2) ODBC driver: The recommended ODBC driver for Microsoft Azure is "ODBC Driver 13 for SQL Server". This ODBC driver can be downloaded from the Microsoft download site. The other SQL Server ODBC drivers are not tested and are not recommended; 3) Behaviors that differ from the regular SQL server: a) Blocking behavior By default, uncommitted operations (insert, update, and deletes) will not prevent any other connection to access the same tables in Azure. This behavior may differ from the regular Microsoft SQL server. Therefore, the -dsd (disable snapshot isolation for download) option should not be used, if the timestamp-based download logic is used in the synchronization. Otherwise it could cause data-inconsistency; b) Column default values Default values support literals and constants only in Azure. Non-deterministic expressions or functions, such as GETDATE() or CURRENT_TIMESTAMP, are not supported.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Well done, finding that!
(it is listed way down under Bug Fixes rather than New Features)
...someone should post the latest read-me files, somewhere 🙂
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Well, apparently the missing support for Azure SQL databases is considered a bug.
...someone should post the latest read-me files, somewhere 🙂
You mean here? 🙂
Well, I like that public resource - but it seems to get updated only now and then, and the readme for 17.0.6 is empty, as I reported a while ago, and newer ones are fully missing.
As you note, this URL works:
http://sqlasupport.sap.com/readme/index.html
However, this one does not:
Instead, it redirects to a location with no SQL Anywhere content:
https://www.sap.com/trends/mobile-technology.html
...shed a tear for SAP Management, they are so very afraid of SQL Anywhere! 🙂
ceased to read on:)
LOL!
...no, wait, that's what I need to do too, to avoid WrongThink!
@Chris, could you also help to maintain/update the published read me files, please...:)
User | Count |
---|---|
60 | |
10 | |
8 | |
8 | |
7 | |
6 | |
6 | |
5 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.