Migration

External Article

Migrating Databases Checklist Part1

  • Article

SQL Server databases move around as an organisation’s data grows, applications are enhanced or new versions of the database software are released. If not anything else, servers become old and unreliable and databases eventually need to find a new home. Here's what to do when migrating your databases.

2013-06-12

4,842 reads

External Article

Oracle to SQL Server, Crossing the Great Divide, Part 3

  • Article

We soon learn, in SQL Server, that heaps are a bad thing, without necessarily understanding how or why. Jonathan Lewis is an Oracle expert who doesn't like to take such strictures for granted, especially when they don't apply to Oracle. Jonathan discovers much about how SQL Server places data, and concludes from his experiments that heaps perform badly in SQL Server because you cannot specify a fill factor for them.

2010-07-23

3,312 reads

Blogs

Who are you? Building an identity map.

By

I admit that until I read the article, Who are you as a Leader?,...

Call a Fabric REST API from Azure Data Factory

By

Suppose you want to call a certain Microsoft Fabric REST API endpoint from Azure...

Distributed Availability Group Dashboard

By

The Distributed Availability Group Dashboard can be downloaded from our GitHub repo. https://github.com/SQLUndercover/UndercoverToolbox/blob/master/DAG%20Dashboard.pbix. This...

Read the latest Blogs

Forums

How to check if credential password for TDE matches the secret key of Key Vault

By Micuen Tabazura

Hi all, In my company we have many databases encrypted with TDE and there...

Create Raw Zone Tables using Generative AI: Data Engineering with Fabric

By John Miner

Comments posted to this topic are about the item Create Raw Zone Tables using...

Database DevOps Metrics

By Steve Jones - SSC Editor

Comments posted to this topic are about the item Database DevOps Metrics

Visit the forum

Question of the Day

Replacing a NULL II

What is returned from this code in SQL Server 2022?

DECLARE
  @value INT = NULL
, @value2 VARCHAR(20) = NULL;
SELECT COALESCE (@value, @value2, 100.5) AS Result;
GO

See possible answers