Changes to a Writable Partition May Fail Unexpectedly
Paul White shows how an update may fail when a partition has some data on a read-only filegroup, and explains several workarounds.
Paul White shows how an update may fail when a partition has some data on a read-only filegroup, and explains several workarounds.
Learn about deadlocks and how you might better troubleshoot the issues involved.
The 2015/16 Simple-Talk Awards have concluded, the votes have been counted and recounted, and the winners have now been announced.
Waterfall is the practice most destructive to developer productivity? Nonsense, according to Phil Factor. Lack of basic team coordination skills comes much higher in the list.
Steve Jones looks at the idea of cataloging our data sets in order to make it easier for
With the new temporal table feature, SQL Server 2016 internally manages two tables: a base table, which contains the latest data all the time, and a history table, which contains a history of all of the changes. Arshad Ali looks at the new feature, how it works, and how to either create a new table with this feature or enable it for an existing table.
Special Characters can lead to many problems. Identifying and reporting on them can save a lot of headache down the road.
With database deployments, not all script-based processes are equal. Some use change scripts in a free-and-easy way, and some, which are normally called ‘migrations-based approaches’, have more discipline around them. In this article, Redgate Product Manager Elizabeth Ayer covers ‘migrations’, and shows some of the benefits that have come with new tooling which is specifically designed to assist the change script processes.
Naming objects and variables in software can create contention in a team. While there are good conventions and standards, ultimately a team just needs to agree on something.
With Fabric Mirroring, Microsoft is promoting a nice and appealing story for operational reporting...
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...
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....
Comments posted to this topic are about the item Extreme DAX: Take your Power...
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