Press Release


External Article

Database Source Control Workshop - London, UK

Redgate's workshops are coming to London on July 8, 2015. In this workshop, you'll learn how to source control your database, deploy your databases from source control, and monitor and track database changes across development, testing, and production environments. Register while space is available.

2015-05-19

7,581 reads

External Article

Automated Database Deployment Workshop: Belfast, Northern Ireland

Redgate's DLM Workshops are coming to Belfast, NI on June 26, 2015. Learn how to: deploy databases using Redgate's DLM tools, assess the different requirements of production and non-production deployments, and handle database administration tasks, such as backups and security, for automated deployment. Register while space is available.

2015-05-15

7,393 reads

External Article

How do you work with databases?

How do you use SQL Server, and how do you expect this to change next year? Fill in Redgate's survey by May 15 and enter a prize draw to win one of 4 $50 Amazon vouchers.

2015-05-12 (first published: )

19,487 reads

External Article

Automated database deployment workshops

Redgate is offering a 1-day public workshop for anyone who’s interested in automated deployments for SQL Server databases. In the hands-on exercises, you’ll learn how to deploy with PowerShell and Octopus Deploy, work with NuGet packages, handle unexpected changes in your production database (database drift), test your changes with dry run releases, add review and rollback steps, check your deployments have worked, and how to fix things if your deployment fails. Find a workshop near you.

2015-05-01

6,632 reads

External Article

Automated database deployment workshop: London, UK

Join Redgate on May 20th for a 1-day public workshop in London. This event is for anyone who’s interested in automated deployments for SQL Server databases. You'll learn how to: Deploy databases using Redgate's DLM tools; Assess the different requirements of production and non-production deployments, and; Handle database administration tasks, such as backups and security, for automated deployment. Register while space is available.

2015-04-29

5,744 reads

External Article

Survey on SQL Server Monitoring

If looking after the health of SQL Server is part of your responsibility, Redgate would love to hear your views on monitoring server health through this 10 minute survey. Complete the survey by May 15th to be in with the chance to win one of three $50 Amazon vouchers.

2015-04-28

7,309 reads

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