The purpose of moving the MS Access database to SQL Azure is to allow remote access by several employees. As long as the client is able to accomplish this task at a reasonable cost then the client will go ahead with the project.
On the one hand there is nothing wrong with reccomending a MS Access/SQL Azure solution to this client. This option will only cost the client an additional $150/year or so. The amount is small enough that the client will view the additional cost as acceptable.
$!50 to place the database on the cloud so several employees can securely access it makes Access/SQL Azure a good match.
One downside to an Access/SQL Azure solution is distributing the solution. Distribution of a Access/SQL Azure solution is not a large barrier. However it still means I need to access to all the employees computers and install MS Access runtime and the Access
front end. Also there will be a set of procedures to handle the program updates.
A better solution to the distribution issue would be to create a WPF application.
However for me the best solution to making the distribution quite simple would be to create a Silverlight application also hosted on Azure. A Silverlight/SQL Azure solution makes the most sense to me. The only downside is the cost. At $1,000 per year to
host one small instance the client will view this amount as too much. For this client only having one small instance fullfills his needs. It is not necessary to have 2 instances to ensure 99+% availability.
I agree using a shared hosting solution at some asp.net would be cheaper. However this introduces another issue. Part of the solution should be having only one provider. Going to the client and saying he now needs to maintain 2 different solutions:
SQL Azure with Microsoft and an asp web site with another provider is not very attractive. If I would go this route I would create a PHP/MySQL solution and not use Azure.
Right now I have two choices for this client if I want to use SQL Azure. I can either reccomend MS Access/SQL Azure for $150/year or Silverlight/SQL Azure for $1,150/year. These are the only two price points that exist for using Azure
at this time. The purpose of my post was that I think there exists a need for another option for clients with low traffic websites somewhere in between these two prices.
In a sense this issue is not a technical issue. This client, and I think many others, do not care or understand that the extra cost is purchasing a dedicated server or all the other capabilities provided by Azure. All the client know is they want
the database on the 'cloud'. It makes no difference what the details are. I think it would be good to have another option to give clients to use Azure. Call this option 'Starter business package' for somewhere around $300 - $500 per year.
I feel that many small businesses will view MS Access/SQL Azure solutions as very attractive for $150/year. It would be good in these situations to also offer small businesses a similar low priced solution for Silverlight/Azure too.
I will check out the OData webservice in the future - thanks,
Dave