The Technical Debt Anchor
Technical debt is something all of us deal with in our systems, and today Steve has a few thoughts on the impact of debt on database sysstems.
Technical debt is something all of us deal with in our systems, and today Steve has a few thoughts on the impact of debt on database sysstems.
Starting in SQL Server 2025, a new edition is available for installation: SQL Server Developer Standard Edition. This article dives into this edition, the problems it solves, and why it is a great addition for development teams that use SQL Server!
What is your choice for data warehousing? Is it a cloud platform? Which one is attractive to you?
Misusing MAXDOP can silently kill performance across your SQL Server. In this deep dive, we uncover how one bad query caused CPU meltdown, run real-world tests, and show how tuning—not parallelism—often holds the true fix.
There are multiple reasons for no full backup: corrupted backups, taking too much time to restore, etc. In this post, I want to show an alternative for these cases, an ace up one’s sleeve, that you can use to recover data.
There is something magical about SQLBits. Whether it is the technical sessions, the sense of community and fun, or the relentless commitment to learning about the latest innovation, this event continues to serve as a pulse check for where data is today and where it’s going tomorrow. This year’s SQLBits at the ExCel in London […]
Learn about a few different options for migrating from Microsoft SQL Server to PostgreSQL.
Steve wonders if it is worth it to use multiple monitoring systems for a database.
Microsoft does not yet support this edition of Ubuntu, but there are some workarounds to make it work. This should not be used for production usage and this blog is for educational/testing purposes only.
Today Steve wonders how many of you might be looking forward to SQL Server 2025 and consider it to be a major release.
By Arun Sirpal
Not every production incident is a database in RECOVERY_PENDING or a corrupted event (like...
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,...
Comments posted to this topic are about the item SQL Art, Part 4: Happy...
WhatsApp: 0817839777 Kw. Industri Pulogadung, Jl. Raya Bekasi Km. 21, Ruko No.A2/18-19, RW.3, Wil,...
WhatsApp: 0817839777 Jl. I Gusti Ngurah Rai No.8 A-B, RT.8/RW.6, Wil, Kec. Duren Sawit,...
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