External Article

Add Additional Nodes to SQL Server 2022 and Windows Server 2022 Failover Cluster - Part 3

I used the guide in a previous tip on Install SQL Server 2008 on a Windows Server 2008 Cluster Part 1 to install a SQL Server 2008 on a Windows Server 2008 failover cluster (WSFC). Now, I would like to upgrade and migrate my SQL Server 2008 failover clusters to SQL Server 2022 running on Windows Server 2022. What is the process for installation and configuration?

SQLServerCentral Editorial

Software Updates, Outages, Processes, and Protocols

This past Thursday, February 22, AT&T had a major outage on their U.S. network. For upwards of 10 hours, hundreds of thousands of customers could not make phone calls, send or receive texts, or use mobile data for apps or browsing websites. Aside from not being able to communicate as normal, it also appeared to […]

External Article

Redgate Summit: The Database Landscape

A series of Redgate events across the globe for data professionals who want to improve their skills and knowledge about Database DevOps, learn about moving to the Cloud, AI, and working across multiple databases. Redgate Summit aims to bring together database professionals who want to level-up their skills to navigate the increasingly complex database landscape. Learn more about emergent technologies, and reliably solve the complex challenges of database management across the entire DevOps lifecycle. Each event will all feature three separate tracks covering New and Future Technologies, Deep Dive Solutions, and Leadership, all promising to equip senior database professionals with the tools and insights needed to navigate the intricate landscape of 2024.

Blogs

Five Ways Redshift Serverless Quietly Eats Your Budget

By

It is Friday, the queries are running, and nobody is watching the bill. That...

A Career of Memories

By

Annabel retired from Redgate Software this week. Across most of my career at Redgate,...

Rethinking Index Maintenance: Why avg_fragmentation_in_percent Is Outdated and What You Should Do Instead

By

As a SQL Server DBA with years of experience tuning production environments, I’ve seen...

Read the latest Blogs

Forums

What is the Cloud?

By Steve Jones - SSC Editor

Comments posted to this topic are about the item What is the Cloud?

Changing the Schema

By Steve Jones - SSC Editor

Comments posted to this topic are about the item Changing the Schema

Index Fragmentation Explained: Page Splits, Logical Reads, and What to Do

By Sanket Parmar

Comments posted to this topic are about the item Index Fragmentation Explained: Page Splits,...

Visit the forum

Question of the Day

Changing the Schema

I set up a few users on my SQL Server 2022 instance.

CREATE LOGIN User1 WITH PASSWORD = 'Demo12#1'
CREATE USER User1 FOR LOGIN User1
GO
CREATE LOGIN User2 WITH PASSWORD = 'Demo12#2'
CREATE USER User2 FOR LOGIN User2
GO
CREATE LOGIN User3 WITH PASSWORD = 'Demo12#3'
CREATE USER User3 FOR LOGIN User3
GO
I then created a schema that one of them owned. Under this schema, I added a table with some data.
CREATE SCHEMA MySchema AUTHORIZATION User1
GO
CREATE TABLE Myschema.MyTable(myid INT)
GO
INSERT MySchema.MyTable
(
    myid
)
VALUES
(1), (2), (3)
GO
SELECT * FROM MySchema.MyTable
GO
I granted rights and verified that User2 could access this table.
GRANT SELECT ON Myschema.MyTable TO User2
GO
SETUSER 'USER2'
GO
SELECT * FROM MySchema.MyTable
GO
This worked. Now, I move this schema to a new user.
ALTER AUTHORIZATION ON SCHEMA::Myschema TO User3;
GO
What happens with this code?
SETUSER 'USER2'
GO
SELECT * FROM MySchema.MyTable
GO

See possible answers