Data Breach Danger
Is a data breach a danger to those identified in the data. A court says no, but Steve Jones wonders if this is a bad decision.
Is a data breach a danger to those identified in the data. A court says no, but Steve Jones wonders if this is a bad decision.
Tara explains when index DMVs gets reset by telling a story from her dark past.
With so many companies looking at other platforms, when should an organization consider changing their database? Steve Jones has a few thoughts.
With the billing data from your Azure Enterprise Agreement collected into one database, it is still necessary to break down the costs and provide access to the correct departments and individuals. This is important for chargeback and further analysis. In this article, Feodor Georgiev demonstrates how to provide granular access to the billing data.
In this tip we look at a simple way to import a simple XML document into a SQL Server table.
A default value has changed in the SSMS v7 restore wizard, and the consequences can be severe.
If you are not managing the transaction log space used by a database, the transaction log might grow uncontrollably. With SQL Server 2017 there is a new dynamic management function (DMF) that exposes statistical information about a database transaction log. One of the things you can do with the information returned from this DMF is to determine how full a database transaction log file is.
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