Scripts

Technical Article

PARSENAME Enhancement

The ParseName function is very useful for getting parts out of a string of characters between delimiters. But a limitiation is that you only can get four parts out, and the function only accepts dots as delimiters.The function I have written below overcomes that limitations, and add a new feature to enable "from left" and […]

You rated this post out of 5. Change rating

2007-08-27 (first published: )

329 reads

Technical Article

Display disk space stats for each table

Here is my replacement for sp_spaceused, I have altered it so that if no table is past in using the @objname parameter it loops through all the tables which is alot easyer than running the old one for each table and it displays the data one result set. So should be easyer to create a […]

(2)

You rated this post out of 5. Change rating

2007-08-23

1,058 reads

Technical Article

Script SQL Server DDL

Scripting SQL Server DDLRichard SutherlandIf you buy into the theory that all database objects should be contained in a source management system such as Visual SourceSafe, and that deployment of database projects should be done from the source management system, then the manner in which Microsoft's Visual Studio 2005 Team Edition for Database Professionals [a.k.a., […]

(3)

You rated this post out of 5. Change rating

2007-08-20 (first published: )

1,414 reads

Technical Article

Prioritize Missing Index Recommendations (2005)

To report indexes proposed by the database engine that have highest probable user impact.  Note that no consideration is given to 'reasonableness' of indexes-- bytes, overall size, total number of indexes on a table, etc.  Intended to provide targeted starting point for holistic evaluation of indexes.

You rated this post out of 5. Change rating

2007-08-17

993 reads

Technical Article

Prioritize Missing Index Recommendations 2 (2005)

This is an enhanced version of my previous script: Prioritize Missing Index Recommendations (2005).To aid in evaluation of whether the recommended index is reasonable, I have added :1. counts for key columns and the total columns of the recommended index  2. the length/bytes for both key and all columns  Note this is 'per row', not […]

(2)

You rated this post out of 5. Change rating

2007-08-17

1,858 reads

Blogs

How AgentDBA Diagnoses SQL Server Issues Fast

By

Not every production incident is a database in RECOVERY_PENDING or a corrupted event (like...

Five Ways Redshift Serverless Quietly Eats Your Budget

By

It is Friday, the queries are running, and nobody is watching the bill. That...

A Career of Memories

By

Annabel retired from Redgate Software this week. Across most of my career at Redgate,...

Read the latest Blogs

Forums

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...

What is the Cloud?

By Steve Jones - SSC Editor

Comments posted to this topic are about the item What is the Cloud?

Changing the Schema

By Steve Jones - SSC Editor

Comments posted to this topic are about the item Changing the Schema

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