Kill User Processes Per Database or Server Wide
Kill any user processes per database or for the entire server instance.
2013-09-05 (first published: 2013-08-21)
1,526 reads
Kill any user processes per database or for the entire server instance.
2013-09-05 (first published: 2013-08-21)
1,526 reads
Found this lovely T-SQL script to display the SELECT statement for any table.
2013-08-22 (first published: 2013-08-06)
3,239 reads
This script shows size information of every database on the instance.
2013-08-21 (first published: 2010-07-26)
5,955 reads
Create views based on table definitions for backwards compatibility when relocating tables to a new database.
2013-08-16 (first published: 2013-07-30)
1,117 reads
Transact-SQL does not have a simple method to launch multiple parallel running scripts. This tool will change the game. It requires SQL Server 2005 or above.
2013-08-13 (first published: 2009-08-28)
17,523 reads
Use this script to find the Stored Procedures which are referencing the table passed as argument from all databases on the server.
2013-08-12 (first published: 2013-08-02)
1,129 reads
Dynamically drop a user from each database on an SQL instance by their server login SID, then remove there server login as well. Plus some helpful printable information when ran.
2013-08-09 (first published: 2013-07-16)
912 reads
Easiest way to search for a string in any object within the database.
2013-08-08 (first published: 2013-07-29)
2,311 reads
A simple T-SQL script to display the number of days since the last database backup.
2013-08-07 (first published: 2013-07-29)
1,662 reads
Outputs an easily readable result of the database and server roles for database principals.
2013-08-05 (first published: 2013-06-14)
1,067 reads
If you’ve been watching AI roll through the data community and thinking, “this seems...
By Arun Sirpal
Not every production incident is a database in RECOVERY_PENDING or a corrupted event (like...
It is Friday, the queries are running, and nobody is watching the bill. That...
Comments posted to this topic are about the item SQL Art, Part 4: Happy...
Hi All I am trying to find 'bad' characters that users might type in....
Comments posted to this topic are about the item Extreme DAX: Take your Power...
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 GOI 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 GOThis worked. Now, I move this schema to a new user.
ALTER AUTHORIZATION ON SCHEMA::Myschema TO User3; GOWhat happens with this code?
SETUSER 'USER2' GO SELECT * FROM MySchema.MyTable GOSee possible answers