We are excited to announce the beta release of SQL Compare & SQL Data Compare 12. We want to use this beta period to get as much feedback from you, the SQL community, as possible. Try it out, or for more information on what’s new, read on.
Jonathan Kehayias takes a closer look at a new trace flag that allows you to process multiple concurrent statistics updates on the same table.
SQL Server 2016 runs faster, sometimes without you changing anything.
This article presents a utility that will show you what SQL statements are using the transaction logs, in terms of log space used and transaction duration.
In SQL Server Master Data Services all the entities are organized in a model. Once a model is ready to be released to subscribers, it should be frozen and marked as ready for subscribers. Until a model is marked as ready, a model is typically deemed as work in progress. In this article, Siddarth Mehta covers the standard process that's required to release a completed version of the model to subscribers.
Knut Jürgensen shares his experiences, both positive and negative, with regard to the function that Master Data Management fulfils within a company. Too often this critical aspect of a business is overlooked or pushed aside without paying it the attention it deserves based on the cost benefits available.
The Stretch database feature in SQL Server 2016 is fantastic, but is it too expensive?
In the third part of his series on Row Level Security (RLS), Greg Larson shows how to disable RLS for database administrators, sysadmins, and database owners.
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