SQL University: Architecting SQL Server Security, the Big Picture
Welcome to this semester's security week at SQL University. In previous semesters we've covered the technical aspects of SQL Server...
2011-02-08
1,933 reads
Welcome to this semester's security week at SQL University. In previous semesters we've covered the technical aspects of SQL Server...
2011-02-08
1,933 reads
Andy Warren has posted another one of his excellent summaries of what’s going on at the PASS Board. Andy, thanks...
2011-02-08
1,580 reads
In the early days of SQL Server you could not run a log backup while a full backup was running....
2011-02-07
1,926 reads
SQL Server PowerShell Extensions (SQLPSX) includes a set of function for working with SSIS which among other things allow you...
2011-02-07
3,226 reads
Don’t let the above title fool you! Have you been confused on the Microsoft SQL Server Licensing requirements? Per Processor, Per CAL, Per Core, Per Socket, Per Node – Per haps (space intended :-), we should revisit the issue again, and try to offer some assistance as you go forward in making your purchasing decisions.
2011-02-04
4,848 reads
Microsoft provides ten years of support (five years Mainstream Support and five years Extended Support) at the supported service pack...
2011-02-04
2,138 reads
31 Days of SSIS
Almost time to wrap up the 31 Days of SSIS. We are down to just two more...
2011-02-03
2,300 reads
I awoke this morning to see a number of stories breaking about the Intel Sandy Bridge H67/P67 Chipset Recall. I...
2011-02-03
1,661 reads
A question came up on the SQL Server Central Forums, how could you use Red Gate SQL Compare to automate...
2011-02-02
2,381 reads
31 Days of SSIS
A day late for the twenty-ninth post of the 31 Days of SSIS, but it is still...
2011-02-02
1,236 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