SQL Saturday #204 - Detroit
Join of for a free day of SQL Server training and networking in Detroit on March 16th.
Join of for a free day of SQL Server training and networking in Detroit on March 16th.
Do the people that build SQL Server really work with it? Steve Jones shares a short story from a recent trip to the Pacific Northwest. This editorial was originally published on May 20, 2008. It is being re-run as Steve is on vacation.
Although databases have no inherent way of recording their version numbers, SQL Server provides the means of doing so, and much more besides. This is a great advantage to anyone faced with the task of deploying databases without errors.
The popular UK conference heads to Nottingham from May 2-4, 2013. Both Grant Fritchey and Steve Jones will be speaking, along with lots of talented SQL Server professionals. Register today.
For enterprise systems, purging data is a reality. Today, we will see some strategies that I recently implemented to make this process work efficiently.
In lesson 3 of the Top 5 Hard-earned Lessons of a DBA series, Brent Ozar exposes six common but scary surprises that can lurk behind the façade of SSMS. Read it now, and learn hard lessons the easy way.
The MERGE statement is powerful and multifunctional, yet it can be hard to master. SOmetimes the MERGE statement that just doesn't do what it's needed to do, like process a Type 2 slowly-changing dimension. Check out this tip to learn more.
The focus of this paper is on the protection of PII data stored within a database using encryption technologies.
The recent decision by Yahoo to end telecommuting elicits some comments from Steve Jones on the topic of remote work.
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