Injecting Your Own Bias
Steve Jones talks about the controversy surrounding the PASS Survey and future Summit announcements. And about how we, as data professionals, might subtly bias clients.
Steve Jones talks about the controversy surrounding the PASS Survey and future Summit announcements. And about how we, as data professionals, might subtly bias clients.
In SQL Server 2008, by default, the option to prevent tables changes is "on". We can have some issues and...
A free one day training event from SQL Saturday and the Birmingham SQL Server groups. Come join us if you are in the area.
In his latest article, Marcin Policht demonstrates a variety of tools that can be employed to execute SQL Server Integration Services packages, focusing in particular on the method leveraging functionality available within the Business Intelligence Development Studio.
Timothy Claason continues talking about database design in a new article. This one talks about expanding the functionality that Bridge Tables provide in your schema.
Learning about practical Integration Services is an important part of the well rounded DBA for the future. Read a sample chapter from this new book.
How to reverse engineer or script a trace for disaster recovery, or simply scripting for enhance and adjustment.
You can earn an MCITPro or an MCM in your DBA career, but there's a world of difference between those two. Steve Jones agrees with Simon Sabin that we need something in between.
Yesterday was the first day of the SQL Server 2008 R2 airlift.I attended a great session on Implementing a Fast...
One of the most useful new features of SQL 2008 R2 for DBA’s is the ability to manage and administer multiple instances of SQL Server from a central location using the new SQL Server Utility tool.
With Fabric Mirroring, Microsoft is promoting a nice and appealing story for operational reporting...
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...
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....
Comments posted to this topic are about the item Extreme DAX: Take your Power...
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