get users across all databases on the SQL Server instance
Quick way to get all users on all Databases
2009-08-05 (first published: 2008-06-06)
1,679 reads
Quick way to get all users on all Databases
2009-08-05 (first published: 2008-06-06)
1,679 reads
Generates a dataset for determining when subscriptions fail to send e-mail or post reports to file shares.
2009-08-05 (first published: 2008-11-19)
1,307 reads
This Script can be used for searching a column in SQL server 2005
2009-08-05 (first published: 2009-07-18)
1,008 reads
This Script can be used for searching a Table in SQL server 2005
2009-08-04 (first published: 2009-07-18)
1,090 reads
Compare SQL code of sp, functions, or triggers. Can run across DB and/or servers. Generates report similar to windif. See details in comments
2009-08-03 (first published: 2008-09-05)
1,115 reads
This Script has been build to list all the tables in a database without using a cursor.
2009-08-03 (first published: 2009-01-05)
2,090 reads
i have recently had the need to search the every database on the server for a particular string.
i came up with this... it has lots of room for improvement but it works
2009-08-03 (first published: 2008-11-11)
1,001 reads
2009-08-03 (first published: 2008-02-29)
3,353 reads
We discovered a need to compress our backups so that we could copy the files over the network to the DR location (log shipping), to save on transfer time during emergency restores.
2009-08-03 (first published: 2009-06-05)
2,520 reads
A set based T-SQL solution for Sudoku puzzle. This is an update to my previous post with some corrections and in-line comments.
2009-07-29 (first published: 2009-07-14)
1,331 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....
WhatsApp: 0817839777 Kw. Industri Pulogadung, Jl. Raya Bekasi Km. 21, Ruko No.A2/18-19, RW.3, Wil,...
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