2018-11-05 (first published: 2018-10-22)
879 reads
2018-11-05 (first published: 2018-10-22)
879 reads
2018-08-08 (first published: 2018-07-22)
431 reads
2018-07-17 (first published: 2018-06-26)
926 reads
It will help to find and manage the users access on DB level
2018-07-05 (first published: 2018-06-26)
421 reads
Script out EXISTING database mail profile settings
2018-04-25 (first published: 2018-04-23)
35,674 reads
It will help to DBA for restrict the SQL Users login from selected applications programs and track there logins with Host name and other details
2018-04-11 (first published: 2018-03-29)
742 reads
It will Help DBA to monitor the instant blocking and can take the action immediately on blocker query and users.
2018-04-05 (first published: 2018-03-22)
1,472 reads
It will help to development team to find their developed & DB server status check.
2018-03-28 (first published: 2018-03-22)
2,590 reads
This procedure will help you to automation of link server failure status check with help of SQL agent job scheduling. Job query :-
exec proc_check_linked_servers 'profiler name','E-mail ID'
2018-02-07 (first published: 2018-01-30)
774 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