schema changes

External Article

Allowing for manual checks and changes during database deployments

  • Article

SQL Change Automation enables users to make database changes to production safely and efficiently using PowerShell cmdlets, which can be integrated easily into any release management tool. This article will show you how to automate database deployments safely, by using SQL Change Automation from within PowerShell scripts, and how a deployment script for a release can be checked and amended as part of the process.

2020-06-15

Blogs

Announcements from the Microsoft Fabric Community Conference

By

(Shameless plug: The price of my book “Deciphering Data Architectures: Choosing Between a Modern...

The Basics of TRY CATCH Blocks–#SQLNewBlogger

By

I was working with a customer and discussing how to do error handling. This...

Working with ALS – Insights from the Ability Summit

By

The 14th annual Ability Summit is a global event that I attended a few...

Read the latest Blogs

Forums

The Journey to Change

By Steve Jones - SSC Editor

Comments posted to this topic are about the item The Journey to Change

Check Azure SQL DB Space Used

By Cláudio Silva

Comments posted to this topic are about the item Check Azure SQL DB Space...

The Cloned Database Size

By Steve Jones - SSC Editor

Comments posted to this topic are about the item The Cloned Database Size

Visit the forum

Question of the Day

The Cloned Database Size

I have a small test sandbox database on an instance with default master, model, msdb, and tempdb settings. The database has these files:database file propertiesI now run this command:

DBCC CLONEDATABASE(sandbox, sandbox_clone);
GO
When I examine the database file properties, what do they show?

See possible answers