Whatever happened to Database Table Refactoring?
Phil Factor ponders why most people lost their initial enthusiasm for refactoring databases iteratively, in parallel with the evolutionary design of the rest of the system.
Phil Factor ponders why most people lost their initial enthusiasm for refactoring databases iteratively, in parallel with the evolutionary design of the rest of the system.
Want to 'trick' SQL Server into performing millions of logical reads to return data, when only are few thousand were really required? In this article, Gail Shaw examines three common forms of generic SQL that can and will confuse the SQL Server Optimizer to the point that it generates and reuses very inefficient execution plans.
Learn how to develop and test a template for logging and error handling in a multi-step SQL stored procedure
Before SQL Server had SQL window functions, SQL Server developers had to use all manner of tricks and algorithms to come up with ways to rapidly process large amounts of data. Do we need these techniques now that we can express a SQL task in terms of window functions? Kathi revisits a famous SQL challenge to find out.
Creating a database in SQL Server running in on-premises with a dedicated storage location for your data in Windows Azure Blob Storage.
If you are deploying SQL Server Availability Groups, one of the important aspects of a successful deployment is monitoring the synchronization of the secondary replica databases with the primary replica - but there are multiple ways to do this. Jonathan Kehayias goes through each, explaining their different benefits and drawbacks.
Marcin Policht gives an overview of automated management features based on the SQL Server IaaS Agent Azure VM extension.
Read a call to get started using Version Control with your database code with a few ideas on how this can help you.
Is there a way to tell who the good developers are? Steve Jones has a few thoughts on why this is an issue.
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