Finding SQL Server objects that reference invalid objects
Since many environments haven't committed to using a source control system, identifying mismatched objects can offer a challenge. Tim Smith offers a solution.
Since many environments haven't committed to using a source control system, identifying mismatched objects can offer a challenge. Tim Smith offers a solution.
As a data guy, I always smile when application developers refer to ‘their’ data. If only it were that simple.
How did you fall in into your particular career? Was it because of a product? Andy Warren talks about his career evolution and how often we become trapped by the products we work with.
I inherited a database that was getting large and not performing well. After adding primary keys life got better.
It's Developer Week in Nuremberg July 14-17. There are a couple of great speakers at this event, like Constantin Small and Sascha Dittmann. Register while space is available
NEO4J, the graph database, can be used to provide answers that are very tricky for relational databases, including providing diagrams to show how SQL tables relate to each other, and the shortest chain of relationships between two tables, as David Poole demonstrates
Do we take security too far? Are we creating unnecessary rules for those that need to use the resources we support? Steve Jones talks today about security and how we might want to approach it when handling rights for developers.
In this tip, Sadequl Hussain outlines what's involved in rolling out a SQL Server instance in RDS. In subsequent tips, he will explore what features it offers and what shortcomings it has.
Phil Factor ponders the preponderance of text in current database tools, and asks what happened to our glorious graphical future?
Continuous Delivery is fairly generally understood to be an effective way of tackling the problems of software delivery and deployment by making build, integration and delivery into a routine. Phil Factor explains why he's an enthusiast for databases being full participants in this story, and suggests practical ways of doing so.
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