The Countdown
Steve Jones has a short piece today, about an announcement coming today at 10am PST during the PASS Summit.
Steve Jones has a short piece today, about an announcement coming today at 10am PST during the PASS Summit.
Setting up multi-node clustered SQL instances from scratch is common practice for companies that want to implement high availability, but adding a new node to an existing clustered SQL instance that has been running for a while may have a few sticking points, especially for a SQL 2005 instance.
My first day in Seattle has ended. My flight arrived around 12:30 and I was in good company with John Lang and Julie Smith on the same flight. We rode the light rail...
The SQLServerCentral 2011 Party at the Summit is getting bigger and bigger. See if you are on the list, and if not, learn how to get your ticket.
A change at the PASS Summit this year has Steve Jones watching to see if it works out well for attendees and speakers.
Data analysis from a cube starts with aggregated and summarized data, followed by drill-down and drill-through of the data for a deeper and intelligent analysis. Drill down is inherently supported when you browse the data of the cube, but drill through has to be defined as per the requirements of analysis. In this tip we will see how to enable drill through on a cube.
This editorial was originally published on Sept 12, 2006. The IRS makes a $318mm mistake and Steve talks about the need to ensure that you don't do something similar.
This article shows an interesting issue with foreign keys and how they are aligned with the base tables in SQL 2005 SP 4.
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