Trigger Based Change Data capture
This script capture INSERTs / UPDATEs / DELETEs on SQL Server table and logs to single table in JSON Format.
2017-12-22 (first published: 2017-12-01)
2,942 reads
This script capture INSERTs / UPDATEs / DELETEs on SQL Server table and logs to single table in JSON Format.
2017-12-22 (first published: 2017-12-01)
2,942 reads
Here is a script that can give the DBA a SQL Instance quick quality check.
2017-12-21 (first published: 2015-01-02)
7,071 reads
Script to grant a SQL a user read-only access to all the databases in Server instance except the system databases and
-- the Log shipped databases(if any : secondary :read-only)
2017-11-22 (first published: 2017-11-14)
23,553 reads
A function to truncate datetimes to month, quarter, hour etc and their multiples for convenient grouping
2017-11-21 (first published: 2017-11-14)
578 reads
https://github.com/ktaranov/sqlserver-kit/blob/master/Stored_Procedure/usp_BulkUpload.sql
2017-11-17 (first published: 2015-05-16)
5,234 reads
Get Logshipping report only when secondary is more than certain time behind Primary.
2017-11-14 (first published: 2017-10-27)
475 reads
With high transactions table the sys.syscommittab table does not gets deleted properly. Millions of backdated row remains. To delete the sys.syscommittab table below is the script.
2017-11-13 (first published: 2017-10-27)
915 reads
SQL Server procedure to script all tables in a given database to one or individual files on a given path.
2017-10-09 (first published: 2017-10-04)
2,947 reads
2017-10-05 (first published: 2017-10-02)
16,597 reads
Lists the job names and package names for jobs that execute SSIS packages (for packages stored in msdb).
2017-09-13 (first published: 2017-09-05)
2,037 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...
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