As data grows and databases become larger and more complicated, data
subsetting provides a method of working with a smaller, lighter copy of a
database to make development and testing faster and easier.
In this article, James Hemson poses the questions; what exactly is data subsetting, how and why are developers using it – or not using it, and
what’s prompting conversations about it?
Love is many a splendored thing. It is also a much-abused word with many different (and twisted) meanings. The type of love I wish to speak about today is not friendship, nor the kind of thing that makes your heart go pitter patter in the springtime, but rather the type of love known as storge, […]
Steve has some advice on how to grow your career by growing your skills and developing deeper knowledge.
This article looks at the basics of the OVER() clause and how the PARTITION section works.
The rise of cross platform databases which are both on-premises and in the cloud, alongside decreasing customer satisfaction and trust in digital channels, has increased the importance - and value - of enhanced database monitoring. Find out how using a database monitoring tool creates value for the whole organization.
This article covers how to use the different date and time functions when working with Spark SQL.
The first three levels of this series have been the lead-up to this level, automating the database deployment with Azure Pipelines. First, we started with an introduction to Azure DevOps and the Git client. Next, SQL Source Control was introduced to manage a database’s schema and manually deploy changes from the database to source control […]
A stagnant career can be stifling, and it can make you unhappy at work, where you spend a lot of time. Steve has a few thoughts on how to avoid that.
Cardinality estimation (CE) is a process used by the query optimizer to estimate the number of rows returned by a query or sub-part of a query. These estimates rely on two underlying things: statistics about the data and a set of assumptions—known as the model.
Welcome to part twenty of the plansplaining series. It has been a long time since I last wrote a plansplaining post, partly because of my health, but also for a large part because I was out of ideas. But recently I decided to dig a bit deeper into a feature that was released in SQL Server 2017 and that I had so far not played with: SQL Graph.
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