Verify Last successful CHECKDB on all databases
Creates a resultset that expresses the last time a successful CHECKDB was performed on every database in the instance.
Does not work on SQL 2000.
2011-09-28 (first published: 2008-03-19)
5,112 reads
Creates a resultset that expresses the last time a successful CHECKDB was performed on every database in the instance.
Does not work on SQL 2000.
2011-09-28 (first published: 2008-03-19)
5,112 reads
Find every object in every database owned by a particular Login.
2011-09-27 (first published: 2008-07-07)
11,335 reads
2011-09-26 (first published: 2011-09-14)
1,812 reads
Generate Script to create all secondary indexes for a database. I have included the ability to generate online indexes if possible and the ability to move to another file group.
2011-09-23 (first published: 2008-07-05)
3,283 reads
A quick procedure to check which full recovery databases have not had a tran log backup in the given period (default is 7 days). This could mean that the recovery mode might need changing or the transaction log backup jobs need investigating.
2011-09-22 (first published: 2007-08-03)
1,713 reads
A set of user defined functions used to calculate the number of business or working hours (excluding the non working hours) that have passed since a certain point of time.
2011-09-21 (first published: 2007-11-20)
3,157 reads
2011-09-20 (first published: 2008-01-11)
2,497 reads
Ensure all your databases have standardised options by running this script weekly.
2011-09-19 (first published: 2007-12-17)
2,141 reads
Just one way of testing for a linked server based on data within your database.
2011-09-16 (first published: 2007-08-07)
2,634 reads
2011-09-15 (first published: 2011-09-05)
2,922 reads
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...
By Steve Jones
Annabel retired from Redgate Software this week. Across most of my career at Redgate,...
Comments posted to this topic are about the item SQL Art, Part 4: Happy...
WhatsApp: 0817839777 Kw. Industri Pulogadung, Jl. Raya Bekasi Km. 21, Ruko No.A2/18-19, RW.3, Wil,...
WhatsApp: 0817839777 Jl. I Gusti Ngurah Rai No.8 A-B, RT.8/RW.6, Wil, Kec. Duren Sawit,...
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