Skip to main content

What is an Azure SQL Logic Server?

This is such a simple question that many times you realize that you do not have no idea about it.
What is an Azure SQL Logic Server Logic? Do I pay for it? Do I share resources between databases inside the Server?

What is an Azure SQL  Logic Server?
Is just a logical grouping of multiple Azure SQL Databases under the same logic server, The server it’s virtual and you do not share any resources cross databases that are deployed under it.
You will share the Server Admin username and password and the name of the server when you want to connect to multiple databases that are under the same Azure SQL  Logic Server.

Do I pay for it?
Know, because behind the science there is no computation allocated to it. For each database that you create under the server, you will specify the tier (size). That is the cost driver for you in the end. Having for example 2 Azure SQL Databases under the same Azure SQL  Logic Server will generate you costs for each database.

Do I share resources between these two databases?
No, the computation and storage resources are not shared. The only things that you share are the ‘master’ users and the DNS name of the database server. Beside this, you also share the master database. This might affect the performance when:

  • Interrogate the master database for scenarios when the number of the databases is close the maximum limit
  • Execute queries against sys.resource_stats (resource utilization)
  • Portal action related to database enumeration 

Things like Firewall, backup retention and access control are managed at Azure Server level.

What are the quotas of Azure SQL (Logic) Server?
The default number of Azure SQL Servers inside an Azure Subscription is 21 and the maximum number of Azure SQL Databases per server is 5.000 (crazy… right?). The maximum number of DTUs per server is 54.000 DTUs.


Popular posts from this blog

ADO.NET provider with invariant name 'System.Data.SqlClient' could not be loaded

Today blog post will be started with the following error when running DB tests on the CI machine:
threw exception: System.InvalidOperationException: The Entity Framework provider type 'System.Data.Entity.SqlServer.SqlProviderServices, EntityFramework.SqlServer' registered in the application config file for the ADO.NET provider with invariant name 'System.Data.SqlClient' could not be loaded. Make sure that the assembly-qualified name is used and that the assembly is available to the running application. See for more information. at System.Data.Entity.Infrastructure.DependencyResolution.ProviderServicesFactory.GetInstance(String providerTypeName, String providerInvariantName) This error happened only on the Continuous Integration machine. On the devs machines, everything has fine. The classic problem – on my machine it’s working. The CI has the following configuration:

TeamCity.NET 4.51EF 6.0.2VS2013
It seems that there …

Fundamental Books of a Software Engineer (version 2018)

More then six years ago I wrote a blog post about fundamental books that any software engineer (developer) should read. Now it is an excellent time to update this list with new entries.

There are 5 different categories of books, that represent the recommended path. For example, you start with Coding books, after that, you read books about Programming, Design and so on.
There are some books about C++ that I recommend not because you shall know C++, only because the concepts that you can learn from it.


Writing solid codeCode completeProgramming Pearls, more programming pearls(recommended)[NEW] Introduction to Algorithms


Refactoring (M. Fowler)Pragmatic ProgrammerClean code[NEW] Software Engineering: A Practitioner's Approach[NEW] The Mythical Man-Month[NEW] The Art of Computer Programming


Applying UML and Patterns (GRASP patterns)C++ coding standards (Sutter, Alexandrescu)The C++ programming language (Stroustrup, Part IV)Object-oriented programming (Peter Coad)P…

Entity Framework (EF) TransactionScope vs Database.BeginTransaction

In today blog post we will talk a little about a new feature that is available on EF6+ related to Transactions.
Until now, when we had to use transaction we used ‘TransactionScope’. It works great and I would say that is something that is now in our blood.
using (var scope = new TransactionScope(TransactionScopeOption.Required)) { using (SqlConnection conn = new SqlConnection("...")) { conn.Open(); SqlCommand sqlCommand = new SqlCommand(); sqlCommand.Connection = conn; sqlCommand.CommandText = ... sqlCommand.ExecuteNonQuery(); ... } scope.Complete(); } Starting with EF6.0 we have a new way to work with transactions. The new approach is based on Database.BeginTransaction(), Database.Rollback(), Database.Commit(). Yes, no more TransactionScope.
In the followi…