And Then There Was One
Windows 2008 RTMs, a change from the SQL Server support team, and a Jump Start for Katmai.
Windows 2008 RTMs, a change from the SQL Server support team, and a Jump Start for Katmai.
Using the Identity Property might be one of the more debated features of SQL Server. This editorial was originally published on Mar 5, 2008. It is being re-run as Steve is on vacation.
In Part 1 of a 3 Part Series Joydip Kanjilal discusses the implementation of a provider independent Data Access Layer in ADO.NET.
Use the power of regular expressions to cleanse your data right there inside the Data Flow. This transformation includes a full user interface for simple configuration, as well as advanced features such as error output configuration.
Windows 2008 RTMs, a change from the SQL Server support team, and a Jump Start for Katmai.
Windows 2008 RTMs, a change from the SQL Server support team, and a Jump Start for Katmai.
Windows 2008 RTMs, a change from the SQL Server support team, and a Jump Start for Katmai.
Using the Identity Property might be one of the more debated features of SQL Server.
Using the Identity Property might be one of the more debated features of SQL Server.
Using the Identity Property might be one of the more debated features of SQL Server.
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...
WhatsApp:0818-751-777 Jl. Kalierang No.Ruko 3-5, Dukuhturi, Kec. Bumiayu, Kabupaten Brebes, Jawa Tengah 52273 (@bcakcpbumiayu)
WhatsApp:0818-751-777 Menara Satu Sentra Klp. Gading, Jl. Boulevard Bar. Raya No.1 Lt. Dasar, 1,...
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