Steps to Drop an Orphan SQL Server User when it owns a Schema or Role
What do you do when you need to remove an orphaned user, but they are the owner of a Schema or Role on that database?
What do you do when you need to remove an orphaned user, but they are the owner of a Schema or Role on that database?
This article describes how to add a log shipping monitor to a log shipping configuration that is already in place.
Today we have a guest editorial from Andy Warren as Steve is on vacation. Was this a good week for you? How do you know? Do you have a definition that helps you determine if it was a good week? Today Andy Warren talks about how we view our jobs.
This is the first in a four-part series on the new AlwaysOn feature in SQL Server 2012. In this article, AlwaysOn is introduced and contrasted with previous high-availability solutions in SQL Server. The second part of the series will commence with a detailed walkthrough on preparing the environment for AlwaysOn
Recently the Azure service had an outage and Steve Jones has a few comments on this and why it might not be worse than your own company's IT group.
In Part 2 of this series we will shred an XML document and insert its records into a SQL Server table using both the OpenXML and XQuery methods.
If you are relying on using 'best-practice' percentage-based thresholds when you are creating an index maintenance plan for a SQL Server that checks the fragmentation in your pages, you may miss occasional 'edge' conditions on larger tables that will cause severe degradation in performance. It is worth being aware of patterns of data access in particular tables when judging the best threshold figure to use.
Find out what SQL Source Control & SQL Compare can do for your database development and deployment processes at one of our free weekly webinars. Each webinar includes a 30 minute software demonstration and a Q&A session.
Learn how to pull the month names in a report drop down using a recursive common table expression (CTE).
By Arun Sirpal
Not every production incident is a database in RECOVERY_PENDING or a corrupted event (like...
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,...
Comments posted to this topic are about the item Extreme DAX: Take your Power...
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
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