Introducing SQL+ Dot Net
SQL+.net is the first real innovation in data access for quite some time, and was built exclusively for SQL developers.
SQL+.net is the first real innovation in data access for quite some time, and was built exclusively for SQL developers.
Protecting Personable Identifiable Information is central to the compliance of numerous regulations which your organization may be subject to. In this article Grant Fritchey starts with the basics of obfuscating address data with the data masking technology in SQL Provision.
T-SQL window functions have been a fantastic addition to the T-SQL language. In this article, Kathi Kellenberger reviews how optimizations available in SQL Server 2019 can improve the performance of these functions.
SQL Census helps users understand who has access to their SQL Servers (including Active Directory groups) and simplify existing SQL Server permissions. A new feature reworks discrete user permissions into database roles, giving users the same effective rights in a more controllable structure. Download and use SQL Census (in preview) for free.
Google and Microsoft have plans for dealing with data incidents. Steve thinks you should as well.
In this tip we demonstrate how to use dynamic SQL and stored procedures to simplify the computation with SQL of one-way and two-way tabulations.
Access OS event viewer and read it from a SSIS package using WMI Data reader task
It seems that many companies are implementing AI into their systems. Steve notes that this isn't always a good idea.
A new error message in SQL Server 2019 will make your life much easier!? Learn more...
Privacy regulations, ranging from GDPR to HIPAA, among many others, put strict compliance requirements on the storage and use of personal and sensitive data. In this article Grant Fritchey explains how the data masking technology in SQL Provision can help you protect credit card data while maintaining characteristics and distribution of the real thing.
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