Developer Deployment Frustrations
SQL Server should work to make it easy for developers to work with it, and include versions like Express in their applications.
2016-10-11 (first published: 2010-09-08)
371 reads
SQL Server should work to make it easy for developers to work with it, and include versions like Express in their applications.
2016-10-11 (first published: 2010-09-08)
371 reads
On Monday, October 24, 2016, there will be a Free-Con in Seattle for those that might not be attending a...
2016-10-11
439 reads
This month is an interesting T-SQL Tuesday topic, and it’s brought to us by Andy Mallon, with the topic of...
2016-10-11
610 reads
2016-10-11
1,385 reads
It’s PASS Summit time and that means Andy Warren and I are doing another Monday Night Networking Dinner.
For those of...
2016-10-10
547 reads
I hope everyone is well in Florida, but the hurricane caused a postponement of SQL Saturday Orlando. Fortunately I caught...
2016-10-07
424 reads
This Friday Steve Jones talks about your support load. Let us know how many databases you support and what the load is like.
2016-10-07 (first published: 2012-10-26)
249 reads
2016-10-07
1,046 reads
Steve Jones says that developers should take responsibility for the code they deploy, perhaps with a warranty of sorts inside their company.
2016-10-06 (first published: 2012-10-22)
160 reads
2016-10-06
1,040 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