Azure SQL Elastic Database Job Agents Configuration


As Database administrator we know that SQL jobs managed by SQL Server agent services, but this concept on SQL Server on-premises, in Microsoft cloud we have another something called Azure SQL Elastic job. Before starting in the definition of it I highly recommend you to understand first what is Azure database deployment model options and How we can configure Azure single database, Azure elastic Pool database and Azure Database Managed Instance Check Below Articles 👇

In this article of today I will cover below points and these points from my view are the basic points still we have many others points in this subject and I will cover it in the upcoming posts, Keep Following me and if you are interested to learn more about Azure SQL Database check this link and if you are interested to prepare for Azure administrator certification AZ-103 or AZ-104 check this link

  • What is the Azure SQL Elastic Job?
  • Differences between Azure SQL Database Jobs and SQL Agent
  • Azure SQL Elastic Database jobs Component
  • Configuration Prerequisites
  • Azure SQL Elastic Job Full Configuration (8 Steps)
  • Review the Elastic Job Configuration
  • References
Continue reading “Azure SQL Elastic Database Job Agents Configuration”

Azure SQL Database Managed Instance Fundamental

SQL Server Managed instance is one of the Azure SQL deployment model options and it is providing 100 % Compatibility with SQL Server on-premises so managed instance it the best migration option when you need to migrate the on-premises database without changing any configuration or losing any features not supported by Azure Single database and Azure SQL Database elastic pool. IF you need to know more information about Azure Single database and Azure elastic pool check this post and if you are interested and preparing for azure administrator AZ-103 certification check this link

  • Azure SQL Manged instance Tips
  • Differences between SQL Server On-Premises and Azure SQL Managed instance
  • Azure Managed instance Service Tier
  • Azure SQL Managed instance Security
  • References
Azure Deployment Model Options
Continue reading “Azure SQL Database Managed Instance Fundamental”

Move Azure Single Database to SQL Elastic Pool

AS I explained before in my previous articles How to provision Azure Single Database and How to Provision Azure SQL Database elastic pool today I will explain How we can move Azure Single Database to New Elastic Pool, For more information about Azure Database Deployment model Check this Post and If you are interested in More Azure Database Articles to check this Link and if you are Preparing for AZ-103 Azure Administrator Certification check this Article, In Microsoft documentation, you will find How to Provision Single Database or Elastic pool Server but you will note find information for How to move Single database to Elastic pool server

Case Scenario

Let us assume that we have 2 Azure Single Database Servers contain 3 Database with different Service Tier and we need to move them to Azure elastic pool

Continue reading “Move Azure Single Database to SQL Elastic Pool”

Azure SQL Database Elastic Pool Fundamental

As we know Azure SQL Database elastic pool is one of the Microsoft Azure database deployment model options to know more about these models check this post and to know more about Azure Single Database check this article and if you interested to check all of the Azure SQL Articles check this link, IF you are Preparing for AZ-103 Azure Administrator Certification check this Article

Azure SQL Deployment Model options
Continue reading “Azure SQL Database Elastic Pool Fundamental”

Azure Single Database Fundamental

AS we now Azure SQL Single database is one from deployment Azure Database models if you need to know more information check this post-Azure Database Deployment model options today I am writing about Fundamental information for Azure Single Database

For More Azure Database Articles Check this Link and If you are Preparing for AZ-103 Azure Administrator Certification check this Article

Create Azure Single Database
  1. The Single Database deployment option creates a single isolated database in Azure SQL Database
  2. Azure Single Database Support DTU-based and Vcore-based Purchased Model
  3. The internal of SQL Database server is hidden from the end-user and all are managed by Microsoft Azure
  4. Azure Single Database has it is own Resources (DTU or V-Core) and this resource will not be shared with other databases in the same single instance. Each Database has dedicated resources.
  5. Single Database Isolated meaning if you created two single databases on the same single database server each Database has dedicated resources and the two databases cannot be communicated together and I think this one is a security feature
  6. This means Azure Single Database is the best option for small workloads with applications connects to one DB.
  7. To Provision Azure SQL Single Database, you need (resource Group, Database name, Server Name, User Name, Password, Location, deployment option either single or elastic pool, Compute Storage and purchase model either DTU-based or vCore-based)
  8. In Azure SQL Single database provisioning you can create new or select existing one from (Resource group and Server name)
  9. In Azure SQL Single database provisioning the (resource Group, Database name, Server Name) Should be a unique name.
Continue reading “Azure Single Database Fundamental”