Scripts

Technical Article

CHECKSUM replacement for TEXT

As we all know, BINARY_CHECKSUM ignores columns of data type TEXT.This code is 100% compatible with MS original. That is, the result is identical.You can use it "as is", or you can use it to see that MS function does not produce that unique values one could expect.

You rated this post out of 5. Change rating

2007-02-13 (first published: )

188 reads

Technical Article

InvalidLogins.pl

Perl script that reports SQL Server AD accounts which are now longer valid by verifying the output of sp_validlogins system stored procedure against SID stored in AD. This is done to ensure only accounts that do not exist are reported since sp_validlogins will only check the name and not SID against AD. Accounts that are […]

You rated this post out of 5. Change rating

2007-02-12 (first published: )

249 reads

Technical Article

Split Function

This is another type of split function which disects 8000 byte varchar with given delimeter and returns table with disected values.It does that with single select statement (internally looped), without using explicit while loop.Works pretty fast

You rated this post out of 5. Change rating

2007-02-06 (first published: )

406 reads

Technical Article

T-SQL Maintenance Plan Creation

Use this script ot be able to create DB Maintenance Plans fast. If you need to create the plans on servers similarly set up, edit the required parameters once, and when you create a new plan, you will only need to specify a database name and one task start time, run the script and the […]

You rated this post out of 5. Change rating

2007-02-05 (first published: )

985 reads

Technical Article

Grant Object Permissions to Role/User in mult DBs

This script cycles through a chosen selection of databases, and grants permissions to all tables, views and stored procedures to a user or role.To use, change the ###text### to control which databases, permissions and the user/role concerned.

You rated this post out of 5. Change rating

2007-02-02 (first published: )

926 reads

Technical Article

Script Login Roles Permissions in all DBs _SQL2005

Usage -Populate @list variable below with account(s),comma delimited list to script. -Save output to recreate:Login,Default DB,Server Roles,DB Access,DB Roles,DB Object Permissions. -- NOTE: -Stored procedures are created in Master, but are deleted -to limit by database see section /*Get a table with dbs where login has access*/ and change the where clause -to script all […]

(8)

You rated this post out of 5. Change rating

2007-02-01 (first published: )

4,442 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