Everki Versa Long Term Review
A couple years I was looking for a new laptop bag. I settled on the Everki Versa, which I’ve been...
2016-08-23
1,169 reads
A couple years I was looking for a new laptop bag. I settled on the Everki Versa, which I’ve been...
2016-08-23
1,169 reads
No matter what we do to secure our databases, we need to be sure our applications are well written, both with secure coding, but also good information handling.
2016-08-23
121 reads
2016-08-23
1,400 reads
Many of us would like to be sure we could rollback changes made during a deployment if they caused issues. Steve Jones notes that it might not be worth actually building those scripts in advance.
2016-08-22
502 reads
2016-08-22
98 reads
One of the things I ran into a few years ago was the idea of a software pipeline. A set...
2016-08-19 (first published: 2016-08-10)
2,813 reads
A smoke test can be a good way to ensure complex systems are working as expected after maintenance or changes.
2016-08-19
961 reads
2016-08-19
1,204 reads
The way that governments build software and work with data must change if we want to be more efficient.
2016-08-18
62 reads
Another post for me that is simple and hopefully serves as an example for people trying to get blogging as...
2016-08-18
634 reads
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....
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