Lawsuits and Data Breaches
Steve Jones notes that a data breach resulted in a lawsuit. How long before that's a common practice, and should we be preparing as data professionals.
Steve Jones notes that a data breach resulted in a lawsuit. How long before that's a common practice, and should we be preparing as data professionals.
The day before SQL Saturday Silicon Valley, SQL Server MVP Steve Jones will be hosting a free seminar in San Jose on March 14 2014. Join fellow database professionals to learn best practices and practical tips for SQL Server version control, continuous integration and deployment.
A common method to detect if a row has changed is to compare hashes. Integration Services itself doesn’t have a hash implementation, so in this tip I’ll show how you can implement a hash detection mechanism using a script component, as an alternative to the pure T-SQL solution.
sp_ExecuteSQL can be used to dynamically execute T-SQL code. Learn how to use it and how to add parameters to control what code is executed.
We might not be able to stop hacks, attacks, or issues with our databases, but knowing that they've occurred is important. Steve Jones notes that we might need auditing more than security.
All DBAs need to engage in a little project management to help make sure everything runs smoothly. In this extract from the book Tribal SQL, David Tate explains his system for managing workload, colleagues, and projects, and how not to be just "the guy who says no".
March 15, SQLServerCentral's Steve Jones and many others (including Kalen Delaney, Kevin Boles, and Karen Lopez) will be presenting at SQL Saturday Silicon Valley. This is a free, one-day learning event about SQL Server, Microsoft Business Intelligence, and Big Data. Register soon while spots are available.
Has the SQLCLR system impacted your SQL Server environment? Steve Jones wants to know if it has or has not today.
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