2019-02-27 (first published: 2019-02-20)
949 reads
2019-02-27 (first published: 2019-02-20)
949 reads
Can be useful when inserting a lot of data into a table.
2019-02-26 (first published: 2019-02-14)
5,347 reads
This script features as we can through the CTE Top10FilesWithLargerDiskConsumption the top ten data files that are showing greater consumption of hard drive related data-reading activities.
2019-01-15 (first published: 2019-01-08)
1,064 reads
Collect CPU % for a time period and alert if Average CPU usage is high
2019-01-14 (first published: 2019-01-08)
1,780 reads
Quick check SQL connection and process details with current SQL text
2018-12-19 (first published: 2018-11-27)
980 reads
2018-11-30 (first published: 2017-04-01)
1,111 reads
2018-11-29 (first published: 2018-11-23)
454 reads
2018-11-15 (first published: 2018-11-08)
1,591 reads
If you have a SQL Server with a High Availability solution (AlwaysOn Availability Groups, Database Mirroring, etc.), and you also have a bunch of jobs which you need to be run on the Primary server only. You need to be able to "failover" the jobs in case the Primary server is no longer Primary.
2018-11-14 (first published: 2018-11-12)
6,026 reads
Create the code to detect and repair non trusted foreign keys
2018-11-13 (first published: 2018-09-27)
712 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