Do Full Backups Break Log Shipping?
TLDR: Nope. Keep on doing your full backups. Make sure that any databases you Log Ship are NOT also doing log backups in your SQL Maintenance Plans, Ola Jobs,...
2021-10-22 (first published: 2021-10-15)
322 reads
TLDR: Nope. Keep on doing your full backups. Make sure that any databases you Log Ship are NOT also doing log backups in your SQL Maintenance Plans, Ola Jobs,...
2021-10-22 (first published: 2021-10-15)
322 reads
SQL Server maintains a variety of stats about all sort of performance items. Index usage (or missing indexes) Query performance Corrupt pages Disk IO performance Way more than I...
2021-10-11 (first published: 2021-09-30)
309 reads
Welcome back to the series “Server Review Essentials for Accidental and Junior DBAs.” So far in this series we’ve taken a look at how to set up your work...
2021-07-06
40 reads
Welcome back to our series, Server Review Essentials for Accidental and Junior DBAs, where we’ve been taking an in-depth look at how to get ready to perform regular SQL...
2021-06-28 (first published: 2021-06-16)
459 reads
Let’s take a look at the final few steps of your initial server intake process and get your workflow up and running as you push toward performing regular server...
2021-04-05 (first published: 2021-03-25)
315 reads
The next post of this series is finally ready to fly. I apologize for the delay between posts, but between the rolling blackouts in Texas during the 2021 Snowpaclypse...
2021-03-18 (first published: 2021-03-15)
329 reads
It’s time for the fourth post in my series about performing regular server reviews. In the first post, we took a look at setting up your local environment. The...
2021-02-09
31 reads
Welcome back to my ongoing series about how we perform regular server reviews here at Dallas DBAs, and the tips and tricks I’ve picked up in my first 1.5...
2021-02-03
31 reads
Welcome back to my Server Review Essentials for Accidental and Junior DBAs series. Last week, we took a closer look at the first steps of getting your environment set...
2021-02-03 (first published: 2021-01-27)
380 reads
Welcome to a new year, and a new look at what I’ve learned in my time as a beginner and junior DBA. So, I’ve been in this DBA gig...
2021-01-28 (first published: 2021-01-19)
661 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