Phil Factor

  • Interests: Motorbikes, Beer, gardening, conservation, Local history.

Stairway to Exploring Database Metadata

Idempotent DDL Scripts That Always Achieve The Same Result - Making Changes Only Once: Stairway to Exploring Database Metadata Level 6

Idempotence is the property of certain operations in mathematics and computer science, that can be applied multiple times without changing the result beyond the first time they are run. When you are making changes to a database to deploy a new version, you need to be sure that certain changes aren’t made twice, or in the wrong order.

★ ★ ★ ★ ★ ★ ★ ★ ★ ★

(6)

You rated this post out of 5. Change rating

2023-10-04 (first published: )

20,222 reads

SQLServerCentral Article

Reading and Writing your Database's Documentation using JSON

One of the problems to which I keep returning is finding the best way to read and apply documentation for databases. As part of a series of articles I'm doing for Redgate's Product Learning, I've been demonstrating how to maintain a single source of database documentation, in JSON, and then add and update the object […]

★ ★ ★ ★ ★ ★ ★ ★ ★ ★

You rated this post out of 5. Change rating

2021-06-28 (first published: )

3,789 reads

SQLServerCentral Editorial

Malleable Source Control

Git has proved to be a better fit to the needs and workflow of a database development team than anything that came before. Git is valuable because it encourages branching and merging, giving more choice in the way that your team can work. Due to the ease with which you can adapt Git, there is […]

★ ★ ★ ★ ★ ★ ★ ★ ★ ★

You rated this post out of 5. Change rating

2021-04-03

269 reads

Stairway to Exploring Database Metadata

Exploring Facts About SQL Server Tables: Stairway to Exploring Database Metadata Level 5

Now that we've explored, in preceding levels, some of the information that is available about indexes, triggers, keys and distribution statistics, we can concentrate on the tables themselves and their columns.

★ ★ ★ ★ ★ ★ ★ ★ ★ ★

(5)

You rated this post out of 5. Change rating

2021-01-13 (first published: )

6,405 reads

Blogs

SSMS Is Getting Smarter—and This Isn’t Just About Writing SQL

By

Continuing with my takeaways from SQLCon and FabCon Europe in Barcelona, let’s talk about...

Yippee-Kai-Yay 2027 Summit in Denver

By

Next year the PASS Data Community Summit is in DENVER! and London, but Denver...

PASS Data Community Summit 2026

By

Yesterday was the first day of sessions at the PASS Data Community Summit (after...

Read the latest Blogs

Forums

Pay for Performance

By Steve Jones - SSC Editor

Comments posted to this topic are about the item Pay for Performance, which is...

BCA KCP Banjaran Adiwerna Hub/Wa. 0817-819-444

By Halo_BCA

Jl. Raya Utara Adiwerna No.304, 306, Pejagan, Adiwerna, Kec. Adiwerna, Kabupaten Tegal, Jawa Tengah...

BCA KCP Ketanggungan Timur Hub/Wa. 0817-819-444

By layanan 24jam BCA

Jl. P. Diponegoro No.141, Dukuhtengah, Dukuh Tengah, Kec. Ketanggungan, Kabupaten Brebes, Jawa Tengah 52663

Visit the forum

Question of the Day

Switching Schemas I

I run this query:

SELECT 
 s.name AS schemaname
 , o.name AS objectname
 FROM sys.objects o
 INNER JOIN sys.schemas s ON s.schema_id = o.schema_id
 WHERE o.name = 'Beer'
I get one row back for an object named dbo.beer. There is an ETL schema and both of these are nonpartitioned tables. I run this code:
ALTER TABLE dbo.beer switch TO etl.beer
What happens?

See possible answers