Editorials

SQLServerCentral Editorial

Free Training

I heard on Thursday a couple weeks ago that someone who had received a free admission to the PASS conference had cancelled and wasn't able to attend. It was last minute and that pretty much ruled out any chance to have a contest, so I called a friend in Denver who's a DBA and doesn't get much of a budget for training. I offered him the admission and he said he'd let me know Friday.

(6)

You rated this post out of 5. Change rating

2007-09-25

1,462 reads

SQLServerCentral Editorial

Billy-yons and Billy-yons of Records

There was an article last week with a great title: The Mother of All Genealogy Databases, and so I had to take a look at it. It talks about some of the large databases on the Internet that are collection public records and linking them together to help people find out about their individual and family histories. The largest site so far, Ancestry.com, supposedly has 5 billion records.

You rated this post out of 5. Change rating

2007-09-24

239 reads

SQLServerCentral Editorial

Opening Day

Today is the opening day for the PASS conference here in Denver and it's kind of exciting. As many of you read this, I've hopefully gotten Simon Galbraith, owner of Red Gate software, and my boss, out here at the ranch shoveling manure. He's anxious to get on the ATV for a ride, so maybe I can work out a deal to reduce my workload 🙂

(1)

You rated this post out of 5. Change rating

2007-09-18

128 reads

SQLServerCentral Editorial

Unethical or Just Sneaky

One of the fundamental rules of a stable, controlled production system is that you apply updates singly, after they've been tested, and you document the change. This way you can ensure that if a problem occurs, you can do some backtracking to see what might have caused instability.

(4)

You rated this post out of 5. Change rating

2007-09-17

1,213 reads

SQLServerCentral Editorial

Recruiters

Do you like recruiters? Do you use them? It's almost impossible not to use them these days when looking for a job. So many of the listings on online job boards are from recruiters and many have deals to place people, so chances are you'll at least deal with on even if they don't get you a job.

You rated this post out of 5. Change rating

2007-09-13

180 reads

Blogs

Prime Day Recommendations

By

It’s Prime Day. A few of my recommendations, since I want to do some...

Fabric for Operational Reporting & SQL Endpoint Trap

By

With Fabric Mirroring, Microsoft is promoting a nice and appealing story for operational reporting...

Crawl, Walk, Run with Agentic Development of Power BI Assets

By

If you’ve been watching AI roll through the data community and thinking, “this seems...

Read the latest Blogs

Forums

SQL Art, Part 4: Happy 4th of July — A British DBA's Guide to Celebrating a War We Don't Talk About

By Terry Jago

Comments posted to this topic are about the item SQL Art, Part 4: Happy...

Finding 'bad' characters

By Barcelona10

Hi All I am trying to find 'bad' characters that users might type in....

Extreme DAX: Take your Power BI and Fabric analytics skills to the next level

By Steve Jones - SSC Editor

Comments posted to this topic are about the item Extreme DAX: Take your Power...

Visit the forum

Question of the Day

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
GO
I 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
GO
This worked. Now, I move this schema to a new user.
ALTER AUTHORIZATION ON SCHEMA::Myschema TO User3;
GO
What happens with this code?
SETUSER 'USER2'
GO
SELECT * FROM MySchema.MyTable
GO

See possible answers