Technical Article

Rename Foreign Key Constraints

This script will rename all FK constraint names in your database.  It will give them a user friendly name that can be used in error messages, etc. The FK contraint names will be formatted as FK_ChildTableName_ParentTableName_soid. Note: You first need to enable 'Allow modifications to be made directly to the system catalogs'. This can be […]

You rated this post out of 5. Change rating

2003-09-19

1,152 reads

Blogs

Redgate Summit Comes to the Windy City

By

I love Chicago. I went to visit three times in 2023: a Redgate event,...

Non-Functional Requirements

By

I have found that non-functional requirements (NFRs) can be hard to define for a...

Techorama 2024 – Slides

By

You can find the slidedeck for my Techorama session “Microsoft Fabric for Dummies” on...

Read the latest Blogs

Forums

Change IN for EXSITS

By Edvard Korsbæk

I have had a hard time to understand how to use EXISTS. I Always...

Error while an ADF pipeline runs stored procedures against Azure SQL Server MI

By river1

Dears, We are using Azure Data factory pipes to run some stored procedures against...

Clear Trace - Asking for SQL Server 2008

By rameshbabu.chejarla

Hi, I have SQL Server 2019 installed and when go the Clear Trace database...

Visit the forum

Question of the Day

The "ORDER BY" clause behavior

Let’s consider the following script that can be executed without any error on both SQL Sever and PostgreSQL. We define the table t1 in which we insert three records:

create table t1 (id int primary key, city varchar(50));

insert into t1 values (1, 'Rome'), (2, 'New York'), (3, NULL);
If we execute the following query, how will the records be sorted in both environments?
select city

from t1

order by city;

See possible answers