Script out EXISTING database mail profile's settings
Script out EXISTING database mail profile settings
2018-04-25 (first published: 2018-04-23)
35,686 reads
Script out EXISTING database mail profile settings
2018-04-25 (first published: 2018-04-23)
35,686 reads
Generate large sample data for your performance and other uses
2018-04-24 (first published: 2018-04-18)
2,918 reads
Update the statistics starting from most accessed and modified ones, with a time limit. Procedure will exit when @MaxExecutionTime parameter is greater than the current execution time.
2018-04-19 (first published: 2018-04-16)
522 reads
2018-04-19 (first published: 2018-04-12)
4,299 reads
This script is used to Find out the table name and column name where a specific string has been used
2018-04-17 (first published: 2018-04-13)
2,111 reads
Script powershell/SMO que gera os scripts de DROP/CREATE para cada JOB existente na instância
2018-04-16 (first published: 2018-04-13)
635 reads
Rename Foreign Key Constraints in a consistent manner. Ideal for preventing constraint errors during code promotion.
2018-04-13 (first published: 2013-03-19)
1,364 reads
It will help to DBA for restrict the SQL Users login from selected applications programs and track there logins with Host name and other details
2018-04-11 (first published: 2018-03-29)
742 reads
It will Help DBA to monitor the instant blocking and can take the action immediately on blocker query and users.
2018-04-05 (first published: 2018-03-22)
1,472 reads
It will help to development team to find their developed & DB server status check.
2018-03-28 (first published: 2018-03-22)
2,590 reads
With Fabric Mirroring, Microsoft is promoting a nice and appealing story for operational reporting...
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...
Comments posted to this topic are about the item SQL Art, Part 4: Happy...
WhatsApp:0817-866-887 Jl. Ahmad Yani No.31, Pattunuang, Kec. Wajo, Kota Makassar, Sulawesi Selatan 90174 (@bcakcumakassar)
Hi All I am trying to find 'bad' characters that users might type in....
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