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.

Comments

Windows Docker Containers can make WIN32 API calls, use COM and ASP.NET WebForms

After the last post , I received two interesting questions related to Docker and Windows. People were interested if we do Win32 API calls from a Docker container and if there is support for COM. WIN32 Support To test calls to WIN32 API, let’s try to populate SYSTEM_INFO class. [StructLayout(LayoutKind.Sequential)] public struct SYSTEM_INFO { public uint dwOemId; public uint dwPageSize; public uint lpMinimumApplicationAddress; public uint lpMaximumApplicationAddress; public uint dwActiveProcessorMask; public uint dwNumberOfProcessors; public uint dwProcessorType; public uint dwAllocationGranularity; public uint dwProcessorLevel; public uint dwProcessorRevision; } ... [DllImport("kernel32")] static extern void GetSystemInfo(ref SYSTEM_INFO pSI); ... SYSTEM_INFO pSI = new SYSTEM_INFO(

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 http://go.microsoft.com/fwlink/?LinkId=260882 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.51 EF 6.0.2 VS2013 It see

Navigating Cloud Strategy after Azure Central US Region Outage

Looking back, July 19, 2024, was challenging for customers using Microsoft Azure or Windows machines. Two major outages affected customers using CrowdStrike Falcon or Microsoft Azure computation resources in the Central US. These two outages affected many people and put many businesses on pause for a few hours or even days. The overlap of these two issues was a nightmare for travellers. In addition to blue screens in the airport terminals, they could not get additional information from the airport website, airline personnel, or the support line because they were affected by the outage in the Central US region or the CrowdStrike outage. But what happened in reality? A faulty CrowdStrike update affected Windows computers globally, from airports and healthcare to small businesses, affecting over 8.5m computers. Even if the Falson Sensor software defect was identified and a fix deployed shortly after, the recovery took longer. In parallel with CrowdStrike, Microsoft provided a too

Cloud as a Story - Vunvulea Radu

Search This Blog