Log Your Changes
How can you maintain a stable environment? Keeping track of all changes is the time-tested and proven technique. Read about it here.
2001-04-30
5,436 reads
How can you maintain a stable environment? Keeping track of all changes is the time-tested and proven technique. Read about it here.
2001-04-30
5,436 reads
Got a plan for moving your data to the new server? Try this one! Andy Warren offers step by step instructions on how to move your data without doing a backup/restore or using detach and attach.
2001-04-30
9,482 reads
The eighth part of Steve Jones's series on having SQL Server automatically report information to a DBA.
2001-04-29
6,710 reads
This week, Brian Knight reviews the book Gurus Guide to Transact SQL.
2001-04-29
5,545 reads
This article shows you in a step-by-step manner how to restore the master database.
2001-04-29
8,966 reads
The seventh part of Steve Jones's series on having SQL Server automatically report information to a DBA.
2001-04-27
4,944 reads
I ran into a dilemma when I was told that I should not allow potential competitors to view my JavaScript comments. If they want to figure the code out; make them work for it.
2001-04-26
3,577 reads
The sixth part of Steve Jones's series on having SQL Server automatically report information to a DBA.
2001-04-25
5,684 reads
This humorous form was originally desgined for Network Admins, but it works for DBAs as well.
2001-04-25
3,480 reads
Everyone needs a stable environment. This article discussed ways to keep your team on the same page.
2001-04-25
5,818 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....
WhatsApp: 0817839777 Kw. Industri Pulogadung, Jl. Raya Bekasi Km. 21, Ruko No.A2/18-19, RW.3, Wil,...
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