Scripts

Technical Article

Stored procedure for viewing trigger details

This is a stored procedure for viewing details of trigger. It accepts trigger name as a optional parameter. When specified, it shows details of only that trigger. If no trigger name is specified shows the details of all the triggers in that database. this SP is created in master database but can be called from […]

You rated this post out of 5. Change rating

2002-06-12

334 reads

Technical Article

Get Notified When Accounts Are Changed

Perfect for finding developers that are changing your database accouts.  This procedure can check the sysusers table for each database and\or the master..syslogins table for account changes.  Gives the option of email notification, logging to a table or both. Update the set statements at the begining of the procedure to configure it however you like.  […]

You rated this post out of 5. Change rating

2002-06-07

524 reads

Technical Article

Proc to Query MSDB..SYSJOBS and SYSJOBSTEPS

TSQL:Procedure to Lookup JobsJack Donnell,jack@JackDonnell.com Have you ever kept altering the same query to look for different items in you database?I took a hint from MS with all the sp_help and other system stored procedures and made a two scripts this one to query for databases scheduled tasks or jobs as they are now called.The […]

(2)

You rated this post out of 5. Change rating

2002-06-07

2,289 reads

Technical Article

Proc to Query Syscomments and Sysobjects

TSQL:Procedure to Query for Dependent ObjectsJack Donnell,jack@JackDonnell.com Have you ever kept altering the same query to look for different items in you database?I took a hint from MS with all the sp_help and other system stored procedures and made a two scripts this one to query for databases dependednt objects or references.I also created another […]

You rated this post out of 5. Change rating

2002-06-07

691 reads

Technical Article

Simple email with CDONTS

Here is a strait forward script that allows you to use CDONTS to send email.  Note that the Subject, From, CC and BCC are all optional parameters.  Because it uses a fully qualified path, this procedure can live in any database on the server.  CDONTS will need to be installed on the server.

You rated this post out of 5. Change rating

2002-06-06

703 reads

Technical Article

sp_lock2  = sp_lock +shows database and object name

sp_lock2 is similar to sp_lock, except that it displays the database name, object name and index name instead of the ids.  It accepts no parameters unlike the sp_lock procedure which can take an optional spid parameter. The basis for the main query which queries the system tables for lock info was taken from the sp_lock […]

(2)

You rated this post out of 5. Change rating

2002-06-06

4,271 reads

Blogs

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

Five Ways Redshift Serverless Quietly Eats Your Budget

By

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

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

BCA KCP Pulogadung Trade Centre Tlp:0817839777

By R4nt4u

WhatsApp: 0817839777 Kw. Industri Pulogadung, Jl. Raya Bekasi Km. 21, Ruko No.A2/18-19, RW.3, Wil,...

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