usp_ShowOrphanUsers - SQL 2k5
Check Orphaned logins ie, not associated with any database on the current instance.
2008-07-16 (first published: 2008-05-20)
1,620 reads
Check Orphaned logins ie, not associated with any database on the current instance.
2008-07-16 (first published: 2008-05-20)
1,620 reads
2008-07-11
436 reads
Best way to monitor Excel, Access, SQL Linked Servers from SQL 2000
2008-07-11 (first published: 2008-06-03)
1,610 reads
Stored procedure which creates snapshot of database. Timestamp in snapshot. Multiple datafiles are supported
2008-07-04 (first published: 2008-05-28)
837 reads
Returns list of active processes and their buffer contents over a specified time.
2008-07-02 (first published: 2008-05-20)
1,476 reads
SHOW WHICH TABLES ARE MODIFIED BY A STORED OR FUNCTION OR WHICH STORED OR FUNCTION MODIFIES A TABLE
2008-06-27 (first published: 2008-05-21)
814 reads
2008-06-26 (first published: 2008-05-20)
924 reads
2008-06-25 (first published: 2008-05-20)
1,270 reads
2008-06-25
324 reads
This will let you know which package had errors rather than sifting through all the package logs one by one.You just need to replace the date.
2008-06-23 (first published: 2008-05-20)
719 reads
It is Friday, the queries are running, and nobody is watching the bill. That...
By Steve Jones
Annabel retired from Redgate Software this week. Across most of my career at Redgate,...
By Tim Radney
As a SQL Server DBA with years of experience tuning production environments, I’ve seen...
Comments posted to this topic are about the item What is the Cloud?
Comments posted to this topic are about the item Changing the Schema
Comments posted to this topic are about the item Index Fragmentation Explained: Page Splits,...
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