Cleanup backup file folder future 7 days
Two PowerShell scripts to create backup folders and clean up old files.
2025-08-29 (first published: 2025-08-16)
337 reads
Two PowerShell scripts to create backup folders and clean up old files.
2025-08-29 (first published: 2025-08-16)
337 reads
This script produces scripts for all the stored procedures in a database.
2025-06-18 (first published: 2025-06-13)
1,054 reads
Semantic versioning (SemVer) is a standardized system for labeling software releases using a three-part number—major, minor, and patch—optionally followed by pre-release labels and build metadata. Comparing semantic versions is complex because it requires handling both numeric and string components, as well as special precedence rules for pre-releases and stable versions. SQL Server’s hierarchyid data type is ideally suited for comparing the numeric parts of semantic versions, enabling efficient and accurate ordering without the pitfalls of string comparison or manual parsing.
2025-05-27
263 reads
This script will help to find orphan users on all databases and will remove them.
2025-05-20
536 reads
2025-05-06
928 reads
This script runs a SQL server Health check for services, databases, Always On, replication, CDC job status.
2025-05-05
1,172 reads
To fetch an execution plan from SQL Server's buffer cache (i.e., the in-memory cache of execution plans), you can query the dynamic management views (DMVs) that SQL Server exposes.
2025-04-30
251 reads
Explanation: sys.databases contains information about all databases on the SQL Server instance. • HAS_DBACCESS(name) = 1 filters out the databases you dont have access to. •ORDER BY name sorts the result alphabetically.
2025-03-04
371 reads
This script will help to get the Database mdf & ldf files size, used space, Free space in MB.
2025-02-27 (first published: 2025-02-25)
391 reads
This T-SQL script helps you monitor the size and status of all databases on your SQL Server instance, providing insights into space usage and performance.
2025-01-29 (first published: 2025-01-20)
970 reads
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,...
By Tim Radney
As a SQL Server DBA with years of experience tuning production environments, I’ve seen...
Comments posted to this topic are about the item What is the Cloud?
Comments posted to this topic are about the item Changing the Schema
Comments posted to this topic are about the item Index Fragmentation Explained: Page Splits,...
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