Azure DevOps

Stairway to Database DevOps

Stairway to Database DevOps Level 4: Creating a new Azure Pipeline (with Azure SQL DB Deployment)

  • Stairway Step

The first three levels of this series have been the lead-up to this level, automating the database deployment with Azure Pipelines. First, we started with an introduction to Azure DevOps and the Git client. Next, SQL Source Control was introduced to manage a database’s schema and manually deploy changes from the database to source control […]

(4)

You rated this post out of 5. Change rating

2023-12-06

2,446 reads

Stairway to Database DevOps

Stairway to Database DevOps Level 1: Setup a Local Git Repo with Azure DevOps

  • Stairway Step

In this first level of the Stairway to DevOps, you will learn how to get version control set up on your local machine and connect to an Azure DevOps repository.

(8)

You rated this post out of 5. Change rating

2023-10-16 (first published: )

3,061 reads

Blogs

AI and Data Engineering on the Edge: The Good, the Bad, and the Overhyped

By

Running AI and data pipelines on the edge instead of the cloud has gone...

UNION vs UNIONALL: #SQLNewBlogger

By

While writing another post I realized my UNION query didn’t work as one might...

T-SQL Tuesday #199 Invitation: Back to on-prem?

By

It’s time for T-SQL Tuesday again! And we’re almost to number 200! T-SQL Tuesday...

Read the latest Blogs

Forums

Secure Cached Plans

By Steve Jones - SSC Editor

Comments posted to this topic are about the item Secure Cached Plans

Complex Data Processing with dbt Python Models: The Fabric Modern Data Platform

By John Miner

Comments posted to this topic are about the item Complex Data Processing with dbt...

Over or Under Provisioned

By Steve Jones - SSC Editor

Comments posted to this topic are about the item Over or Under Provisioned

Visit the forum

Question of the Day

Secure Cached Plans

The DMV, sys.dm_exec_cached_plans, contains rows for each cached plan on an instance. In Azure SQL Database, not every used has rights to every database, as there does exist an instance behind each database. How is security handled for this DMV in Azure?

See possible answers