Find Invalid Objects in SQL Server
This article shows how you can find which objects in your database might not be valid after schema changes.
This article shows how you can find which objects in your database might not be valid after schema changes.
This editorial was originally published on Jan 16, 2007. It is being republished today as Steve is on vacation. This one looks at the potential issues with data mining when data might be shared between companies.
Learn how to configure Azure SQL Database and setup the AdventureWorks database for code testing and learn how to use features of SQL Server.
From castles and dragons to swordfights and spells, this year’s SQL Bits will have it all. Make sure you don’t miss out on our great sessions, from Code Errors to Reliable Releases, to adding some PostgreSQL skills to your repertoire. Come and say hi to us at the Redgate booth! Get 10% off registering with 10REDGATE.
I honestly enjoy writing editorials. Something pops into my tiny brain next to something else, and I'm off. However, today, as I started to write on the topic of learning, I suddenly felt like I had just written this same editorial. I go and look, sure enough, several of my recent editorials have been on […]
Steve thinks the world is close to normal for him after the pandemic. What about you?
Learn how you can use CI/CD with your ADF Pipelines and Azure DevOps using ARM templates.
Missed our recent webinar on ‘Monitoring: The ROI of Build vs Buy’? Catch up on demand and find out the pros and cons to building a monitoring system versus purchasing one. Watch now!
Learn about the SELECT DISTINCT SQL command to return a unique list of values from SELECT queries along with several examples.
Not only is the security of our organization important, but that of our partners matters as well.
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