Effective Engineering
Platform engineering is a new area of focus for some, but it's already being seen as passé by some. Steve notes that there isn't a magic bullet for building better software. It comes about by us working together.
Platform engineering is a new area of focus for some, but it's already being seen as passé by some. Steve notes that there isn't a magic bullet for building better software. It comes about by us working together.
This tip covers the differences and similarities between SQL Server index rebuild and index reorganize operations.
Have you ever been stuck in some area of your life? Maybe at work? That big project. Progressing in your career. The slow query that seems impossible to make faster. Learning new skills to switch careers. Maybe outside of work? The weekend home project that’s been going on for more than a few weekends… possibly […]
Azure Data Studio (ADS) is a lightweight IDE built...
Many years ago, my wife and I wrote an article for Datamation, a major trade publication at the time, under the title, “Don’t Warehouse Dirty Data!” It’s been referenced quite a few times over the decades but is nowhere to be found using Google these days. The point is, if you have written a report using data, you have no doubt felt the pain of dirty data and it is nothing new.
Join over 170 global data experts offering more than 150 sessions designed for all skill levels. Explore the schedule to plan your days on-site, secure your ticket, and book your travel before prices increase.
Steve is a little disappointed in technology that didn't work well after a security incident.
When you build applications that store data in SQL Server you will most likely have to store dates and times, and you’ll call functions to do date manipulations. It is important to understand the different date and time data types, and when to use one data type over another. In this level I will be exploring the different date and time data types and discussing when each type is appropriate.
This article explores how raising the Cost Threshold for Parallelism (CTFP) affects missing index recommendations in SQL Server along with examples.
If you’ve been watching AI roll through the data community and thinking, “this seems...
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...
Comments posted to this topic are about the item SQL Art, Part 4: Happy...
Hi All I am trying to find 'bad' characters that users might type in....
WhatsApp: 0817839777 Kw. Industri Pulogadung, Jl. Raya Bekasi Km. 21, Ruko No.A2/18-19, RW.3, Wil,...
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