Microsoft SQL Server Databases on the Azure Cloud
Microsoft Azure lets you economically and quickly host enterprise quality SQL Server databases in the cloud. The cost of each database is relatively modest.
Managing Resources and Costs for Individual Databases
However, as you add more databases, larger databases, and/or databases that require more resources, costs increase. Providing more resources to a database is helpful when it demands it, but when users aren’t on it or during non-business hours, it may be wasted capacity. Even during business hours, one can have some databases being utilized more than others at unpredictable levels.
Pooled Resources Across Multiple Databases
Fortunately, Azure offers an Elastic Pool option to share resources across multiple databases. If the demand on your databases is inconsistent (spiky), you can provide a high level of capacity that’s available to the most demanding database while allowing other databases to share those abundant resources when needed.
- You no longer need to set the limits of each database,
- You are not charged a per database monthly fee which is great for supporting lightly used databases.
Migrating Existing SQL Server Databases to Elastic Pool
Microsoft provides information on SQL Elastic Pools but does not explain how to convert existing databases to an Elastic Pool.
FMS President Luke Chung wrote a new paper with step-by-step instructions on how to convert existing SQL Server databases on Azure to an Elastic Pool without the need to change the database connection strings:
Converting Microsoft Azure SQL Server Databases to SQL Elastic Pools to Share Server Resources
Here’s more information on Designing and Deploying Microsoft Azure Solutions
Microsoft Azure lets you easily create and deploy enterprise quality SQL Server on the cloud and scale it to suit your application’s needs. From the SQL Server database’s Azure dashboard, you can see the Database Transaction Unit (DTU) usage against the specified DTU limit for the database.
One Hour Usage Graph
This is what we saw for usage over one hour. The cyan line across the top is the DTU limit. The dark blue line is the DTU used. The limit is what you pay, so it’s important to scale it to what the application needs.
One Hour Azure SQL Server DTU use versus limit
While everything seemed fine at the weekly level, looking at the hourly graph gave us a shock. It looks like the database is maxed out for most of the hour. It seems conclusive that we need to increase our DTU level.
65 Minute Graph
But when we set the range to 65 minutes and saw this:
65-minute Azure SQL Server DTU use versus limit
These are completely different displays of the same period of time. The 65 minute graph never hits the maximum DTU. What’s going on?
Visit our page Monitoring SQL Server Usage on Microsoft Azure and Setting DTU Limits for an explanation.
We’ve completely revamped our Microsoft Access to SQL Server Upsizing Resource Center. Find links to all our related white papers and Microsoft resources to help you with the SQL Server upsizing process, from deciding why and which Microsoft Access databases to upsize, the different options, and using SQL Server Express.
We have several new and updated resources:
- Microsoft SQL Server Express: Version Comparison Matrix and Free Downloads
For the first time, all the different versions of SQL Server Express from 2005 to 2014 are shown, compared, and referenced with download links. This content required extensive research to document the details of which operating system each SQL Server version supports. Just because Microsoft web pages list the versions they support doesn’t necessarily mean it works when you actually try to install it.
- Automating the Backup of Your Microsoft SQL Server Express Databases
If you’re using SQL Server Express, you still need to create backups of the database. Here’s how to automate it.
- When and How to Upsize Microsoft Access Databases to SQL Server
The original version of this was written for Microsoft when they selected us for a joint national campaign a decade ago to promote Microsoft Access to SQL Server Upsizing. We’ve updated it to better explain why and why not people should upsize their Access databases and an overview of what the options are and what to do.
Hope this helps!
We are very pleased to announce our new technical support site (http://support.fmsinc.com) to provide forums and the ability to submit technical support inquiries.
Our new site lets you submit requests and respond to them via email with our support team. It also lets you visit our site to check the status of your requests and their entire chain of communications. You can login directly or use affiliated logins from Facebook, Google, and Twitter.
You can also read information and ask questions to the community on topics related to Microsoft Access, Visual Studio, LightSwitch, and SQL Server. We hope you’ll join us.
Additional support resources are available here:
Last month I spoke at the Portland Access Users Group Conference at Silver Falls State Park. I gave a presentation introducing Visual Studio LightSwitch and how it could be used for SQL Server applications deployed on a variety of platforms. As a follow-up, I’ve created a summary matrix and discussion that highlights the features and limitations of the variety of platforms from Microsoft Access, Visual Studio LightSwitch, and Visual Studio.
Microsoft Access started at the beginning of the Windows revolution 20+ years ago and became the most popular database of all time. More recently, additional technologies have become significant, so it behooves the Microsoft Access community to be aware of the trends and options.
Ultimately, it’s about being able to create solutions that help you and/or your users accomplish their mission. Sometimes the user’s platform is critical, sometimes, it’s the data source, and other times it’s the permissions you have to deploy a solution. A variety of platforms and options are available with benefits and limitations with each. Meanwhile, Microsoft Access is also evolving with their latest Access 2013 version offering new web based solutions.
We’ve written a new paper Comparison of Microsoft Access, LightSwitch and Visual Studio Platforms for Database Developers that summarizes what we’re seeing and experiencing.