Data Types - Does size really matter? - nvarchar vs. varchar
How many of us have created a new table and used the default and first data type nvarchar for all of the text/alphanumeric fields, or had...
2023-08-18
6 reads
How many of us have created a new table and used the default and first data type nvarchar for all of the text/alphanumeric fields, or had...
2023-08-18
6 reads
A client asked for a summary of changes, so I wrote this quick post to show where to find this in SQL Compare 15. If you use SQL Compare,...
2023-08-18 (first published: 2023-07-31)
189 reads
I’m back from an office trip this week to Pasadena. I had the chance to go to the office, do some internal training for people, and spend time with...
2023-08-18
42 reads
Met an eager young volunteer at SQLSatBR over the weekend who inspired me to update a blog post that hadn't been refreshed in a few years. See the [UPDATED] Training...
2023-08-18 (first published: 2023-07-31)
610 reads
As a part of a recent Data Exposed that I was on, there was an ADS update which mentioned Copilot being added. Since I’ve been experimented, I decided to...
2023-08-17
93 reads
Looking to attend a security summit in cooler weather that will benefit students? Applachian State holds an annual cybersecurity summit and this year it is scheduled for September 8,...
2023-08-17
38 reads
A Basic SQL Script to Monitor Long Running SQL Server Agent Jobs
As a SQL Server DBA, especially Production/Operations DBA in a relatively large environment,...
2023-08-16 (first published: 2023-07-31)
1,099 reads
Creating a data warehouse can be challenging. Identifying the grain is one of the most important parts of having a quality data...
2023-08-16
4 reads
Inside Redgate Software, someone posted a picture and was asking if anyone knew who the person was. In this case, there had been a conversation at an event, and...
2023-08-16
42 reads
It’s been a bit since I did one of these so let’s go back to the basics. Best practices. We ... Continue reading
2023-08-16 (first published: 2023-08-01)
512 reads
It is Friday, the queries are running, and nobody is watching the bill. That...
By Steve Jones
Annabel retired from Redgate Software this week. Across most of my career at Redgate,...
By Tim Radney
As a SQL Server DBA with years of experience tuning production environments, I’ve seen...
Comments posted to this topic are about the item What is the Cloud?
Comments posted to this topic are about the item Changing the Schema
Comments posted to this topic are about the item Index Fragmentation Explained: Page Splits,...
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 GOI 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 GOThis worked. Now, I move this schema to a new user.
ALTER AUTHORIZATION ON SCHEMA::Myschema TO User3; GOWhat happens with this code?
SETUSER 'USER2' GO SELECT * FROM MySchema.MyTable GOSee possible answers