Miscellaneous

SQLServerCentral Article

Mind Your Manners

  • Article

Whether you use the forums here or post questions in the venerable Usenet usegroups, there are some basic courtesies you should follow. Sushula Iyer takes a minute to list some things that might help you get your next question answered quickly and completely.

(6)

You rated this post out of 5. Change rating

2006-10-18

4,618 reads

Technical Article

Switch Databases

  • Script

This script changes the physical, logical and file names of a database.  It stores the current database until the next time the script is run, and creates a dummy database for the next update.  The intent was to have minimal downtime even though the load (import, snapshot, etc.) may take a long time.  Three copies […]

You rated this post out of 5. Change rating

2007-02-22 (first published: )

668 reads

Technical Article

Proper Luhn AddCheckDigit for any length #

  • Script

Most of the luhn scripts assume that you are working with credit-cards and then IMPROPERLY calculate their luhn check-digit by starting at the left side (assuming that the core number is always 15 digits).  However, if you don't know the length of your core number, then such an approach will fail when the length is […]

(1)

You rated this post out of 5. Change rating

2006-10-10

283 reads

Technical Article

scrript to convert datatypes of multiple columns

  • Script

generates an runs a select statement to convert all th olumns of a certain datatype in apirticular table to another datatype:eg all columns of type int to varchar etc the sp takes three parameters namely the table name, source data type and detination data type generates a select query ad executes it eg: exec ConvertTableTypes […]

You rated this post out of 5. Change rating

2007-07-10 (first published: )

191 reads

Technical Article

Detect invalid FK-data after using "WITH NOCHECK"

  • Script

In situations where FK's have been created using the "WITH NOCHECK" option you can get into troubles because the FK-data is not checked ! (so there may be invalid data in the FK-column !)E.g. ALTER TABLE [dbo].[mytable] WITH NOCHECK add constraint [FK__USED_RESO__Actio__1162CF5F] FOREIGN KEY ( Action_Type ) REFERENCES [dbo].[Action_Types] ( Action_Type ) BOL states "... […]

You rated this post out of 5. Change rating

2007-05-29 (first published: )

556 reads

Blogs

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

How AgentDBA Diagnoses SQL Server Issues Fast

By

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

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