Home/ Questions/Q 7617537
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-31T03:10:30+00:00

We’re getting ready to build a new platform for our current system. Currently we

  • 0

We’re getting ready to build a new platform for our current system. Currently we install sql server express locally to all our clients and all their data is stored there. While the process works pretty good, it’s still a pain to add columns/tables etc. We also want to have our data available outside of the local install. So we’re moving to a central web based sql database and creating a web based application. Our new application will be a Silverlight 5, wcf ria services, mvvm, entity framework application

We’ve decided that either a web hosted sql server database or sql azure database are the way to go. However, I have no idea why I would choose one over the other. The limitations of azure don’t seem to apply to us, but our application will be run on our current shared web host. Is it better to host the application on the same server as the database? Do we even know with shared web hosting that the server is on the same location as the app? There’s also the marketing advantage of being ‘in the cloud’ which our clients love when we drop that word (they have no idea about anything technical, it’s just a buzzword for them). I’m not too worried about the cost as I think both will ultimately be about the equivalent of each other.

I feel like I may be completely overthinking this and either will work, however I’d like to try and get the best solution for us and don’t want to choose without getting some feedback.

In case it helps, our application is mostly dashboard/informational data. Mostly financial and trending data. It’s almost entirely read only. Sometimes the data can get fairly large and we would be sending upwards of 50,000 rows of data to the application.

Thanks for any help/insight you can provide for me!

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    The main concerns I would have with using a SQL Azure DB from an application on your current shared web host would be

    1. The effect of network latency: Depending on location, every time you do a DB round trip from your application to the SQL Azure DB you will incur a 50-100ms delay. If your application does lots of round trips, this will mount up. Often, if an application has been designed to work with a DB on the LAN (you use of local client DBs suggests this) the they tend to get “chatty” since network delays are very small on the LAN. You may find your application slows down significantly.

    2. Security: You will have to open up the SQL Azure firewall to the IP address(es) that your application presents when querying. Depending on your host, it may be that this IP address is shared between several tenants. This would be a vulnerability.

    If neither of these is a problem, then SQL Azure will provide a much lower management overhead (e.g. no need to patch etc.) and will give you very high reliability, especially in terms of the risk of data loss.

    • 0