WITH DATA_PURITY (from recent experience, the key to knowing if patching to 14.0.3015.40 was okay)
So there I am, all keen on keeping ahead of the latest security issue, as usual, whilst handling my patching...
2018-01-07
482 reads
So there I am, all keen on keeping ahead of the latest security issue, as usual, whilst handling my patching...
2018-01-07
482 reads
Just a quick note to share last Wednesday night's presentation on how to manage SQL Server vulnerabilities, plus a first...
2017-11-27
556 reads
Assess your vulnerabilities before a system compromise brings it all down: just like what wasn't done early morning on Zhiggy's...
2017-07-26
798 reads
I had a note (or ‘action item’) to make sure that people were informed regarding the ‘uninstall’ of SQL Server,...
2016-07-12 (first published: 2016-06-29)
88,168 reads
Speaking next Wednesday, Vermont SQL PASS group, thanks to Roman Rehak? for the invite! http://www.meetup.com/VTCode/events/223946011/
I'll be doing an update to...
2015-07-17
708 reads
For years now we have dropped using Cat6 at home for Wifi,
since the Cat5e cables in the house we moved...
2015-01-04
1,168 reads
Thanks to the perseverance of SQL MVP Shehap El-Nagar’s invite last year, this brave
man from the Saudi Ministry of Higher...
2014-09-11
1,543 reads
On August 12th, 2014, another infamous ‘patch-Tuesday,’ Microsoft released a series of Security Updates for multiple versions of SQL Server,...
2014-08-22
1,989 reads
Now that it has been a
good five years I have been blogging away here and on SSC, the editors recently thanked
us...
2014-05-12
1,049 reads
For those planning a move to SQL Server 2012, although this process can apply for many Database Migrations, perhaps this Microsoft...
2014-01-13
10,795 reads
By Steve Jones
It’s Prime Day. A few of my recommendations, since I want to do some...
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...
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