My questions answered on SQL Mobile

Q: [6] what are the scenarios for adding multiple devices (and consequently multiple SQL Server Mobiles) to sync with a single server and single SQL Mobile to sync with multiple SQL Servers?
A: Case studies @ http://www.microsoft.com/sql/ce/productinfo/casestudies.asp would tell you mostly about why multiple SQL Server Mobiles are needed against a single SQL Server database.
Q: [9] what are the scenarios for adding multiple devices (and consequently multiple SQL Server Mobiles) to sync with a single server and single SQL Mobile to sync with multiple SQL Servers? - i wanted to understand the technical scenarios for multiple sync.
A: There are many scenarios where multiple sync can be a very useful feature. I'll explain one such scenario here. Take for example a courier company which has 1000 trucks to deliver couriers to all parts of a city. Each truck driver has a mobile device to improve his productivity. How would you leverage on these mobile devices and come out with the best technical solution to implement this? Here's how - Store all data in a central MS SQL Server database and make it a publisher. Create multiple subscriptions, one for each device that your drivers have. A SQL Mobile based application runs on each device and subscribes to the backed SQL server database. Every truck would have its own payload and would get only its data from the server. I'll be answering the second part of your question too.

Q: [9] what are the scenarios for adding multiple devices (and consequently multiple SQL Server Mobiles) to sync with a single server and single SQL Mobile to sync with multiple SQL Servers? - i wanted to understand the technical scenarios for multiple sync.
A: Second part of your question was - technical scenario for single SQL Mobile to sync with multiple SQL servers. Lets say you have to design a "reporting on the move" employee payroll reporting application for the management team of your company (lets say 100 people) where each member of team has a mobile device. How would you design this? Here's how - All payroll data would already be available on backend SQL Server databases. However, most of the data would be distributed amongst different databases and different tables in the databases. To generate a report, you would want to pull data from multiple SQL Server databases and tables (employee table, salary table, payroll metrics table etc). In this case, your SQL Mobile based reporting application will have to subscribe to multiple backend SQL Server databases.

Q: [18] is there a deployment story? if i have to deploy SQL MObile solution to 1000 devices alongwith the relevant subscriptions what is the recommended way?
A: Yes, with SQL Mobile 3.0 you can infact created the initial subscription on the desktop using SQL Server Management Studio. Then you can copy that database to hundreds of mobile devices. Yet, the Identity Range Management takes care of getting you different identity numbers generated for different devices even when you are offline. However, after copying the DB onto the device. This is really cool as at the initial subscription time, we will have huge data to be downloaded and this can be done on the desktop now using SQL Mobile 3.0.
-------------------------------------------------------------------------------
This posting is provided "AS IS" with no warranties, and confers no rights.

Comments

Popular posts from this blog

My family genealogy : Kurmi

Solving the multi-platform challenge in mobile devices

How to report software piracy in India