Check existence of a database
Check Status of a database. It will loop through all databases and will print message if the db is present.
2019-05-03 (first published: 2015-04-10)
1,328 reads
Check Status of a database. It will loop through all databases and will print message if the db is present.
2019-05-03 (first published: 2015-04-10)
1,328 reads
Execute the function and pass only the SQL Server Name to check if the SQL Instance is available and if yes, what is the Instance Type.
2019-05-03 (first published: 2015-03-26)
1,317 reads
Check all the running SQL services in different servers.
You can use the details before you start implementing SQL Patch to the servers i.e. if you want to explicitly stop the SQL Services.
2019-05-03 (first published: 2015-03-26)
2,118 reads
If you have any requirement to check the size of each sub-folders in a path, you can use my script.
2019-05-03 (first published: 2015-05-20)
1,672 reads
Using Powershell, Cleanup Older than 30 days of Files & Folder through SQL Job
2019-05-03 (first published: 2015-08-04)
2,607 reads
2019-05-03 (first published: 2015-05-15)
1,613 reads
If you have a requirement where you need to copy all your backup files to any remote shared location from your local folder/drive and after that you need to do a periodic cleanup of the backup files, you can use my script.
2019-05-03 (first published: 2015-06-01)
2,080 reads
Server principal 'xx\yy' has granted one or more permission(s). Revoke the permission(s) before dropping the server principal. (Microsoft SQL Server, Error: 15173). If you are gett
2019-05-03 (first published: 2016-09-16)
3,132 reads
2019-05-03 (first published: 2015-05-05)
2,343 reads
IF you have need to schedule job to cleanup backup files older than N days, you can use my written script.
2019-05-03 (first published: 2015-06-04)
666 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