2021-02-16
5,218 reads
2021-02-16
5,218 reads
Earlier today, a revolutionary product was released: a universal data integration utility.
2015-04-01
6,687 reads
I became a SQL guy back in 1998 because the company that hired me used SQL Server. It’s been a good ride and it’s paid the bills, but after 15 years or so it’s time to do something different.
2015-04-01
6,297 reads
In the world of data it’s always been about speed. SSD’s have become very common on consumer machines and not unusual in corporate datacenters.
2014-03-31
3,135 reads
The PASS Summit is just over a week away, and one again Andy Warren and I are hosting a networking dinner on Monday night. This is a free, informal event to help people get to know each other. Whether you are new to the community or have been to many events, you’re welcome to attend.
2013-10-14 (first published: 2013-10-04)
1,371 reads
If you’re involved in the database world it’s hard to have missed the rise of the “no-sql” database products, designed to – depending on your view or the product I suppose – make databases simpler, break out of the transaction database paradigm, scale out across hundreds of machines, make it easy to change the db design (or not require one). I think some of the problems no-sql tries to solve are real, others reflect a lack of awareness/training/tools on how and why relational databases could not just solve the problem, but solve it better.
2013-04-01
3,528 reads
PBM raises errors for policy violations. We can create alerts on those errors to be notified of policy violations. In order to setup alerts on these errors there are three prerequisites. Note that violations for the “On Demand” evaluation mode do not raise errors. A policy must be set to
2011-12-09
1,094 reads
Extended events have been a bit of a personal “Elephant in the room” for me. I know they are there and I should really get on a start using them but never *quite* have a compelling enough reason.
2011-12-08
1,538 reads
My first day in Seattle has ended. My flight arrived around 12:30 and I was in good company with John Lang and Julie Smith on the same flight. We rode the light rail...
2011-10-12
642 reads
For Day 7 of this series, I will talk about the incredibly useful CPU-Z utility, which is available for free...
2011-04-11
1,791 reads
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