Bad Days
This Friday Steve Jones wants you to look back and cringe a bit. Share with the rest of the community what a bad day was for you and see if it was really as bad as you think.
This Friday Steve Jones wants you to look back and cringe a bit. Share with the rest of the community what a bad day was for you and see if it was really as bad as you think.
It's 15 years after the beginning of the century. Time to eliminate the security exposure of SQL logins, and implement integrated security. Active Directory Groups make this easy for the DBA.
In this tip, Edwin Sarmiento looks at how to create the Always On Availability Group with a listener name when using SQL Server on Linux.
Explore Batch Mode Memory Grant Feedback that was introduced in SQL Server 2017
Python is a versatile language that is gaining more popularity as it is used for data analysis and data science. In this article, Rick Dobson demonstrates how to download stock market data and store it into CSV files for later import into a database system.
In this new article, we will show how to audit the Data Warehouse Activities.
We are busy as administrators, and it can be very useful to ensure our systems avoid adding to our workload.
Tara Kizer talks identifying THREADPOOL waits and what you can do about them.
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