Outsourced = Laid Off?
This editorial was originally published on May 3, 2006. Steve is traveling in the UK this week and we are reprinting older pieces. This one looks at offshoring.
This editorial was originally published on May 3, 2006. Steve is traveling in the UK this week and we are reprinting older pieces. This one looks at offshoring.
There is a popular design for a database that requires a built-in audit-trail of amendments and additions, where data is never deleted, but superseded by a later version. Whilst this is conceptually simple, it has always made reporting the latest version of data complicated. Alex Kuznetsov joins the debate on the best way of doing this with an example using an indexed view and the filtered index.
This editorial was originally published on Feb 19, 2006. We are reprinting pieces this week as Steve is traveling in the UK.
In this article Tom Thomson takes a look at what second normal form means, how it is violated, and how you can fix it. This is part of our normalization series.
We're pretty confident that we have locked down and encrypted our financial data, but a lot of our customer's PII (Personally Identifiable Information) data is still held in unencrypted form. This data is able to be selected directly by read only business users on many of our downstream reporting, datawarehouse and standby servers. The rise of identity theft makes protecting this data imperative. DBAs are the custodians of this information and must protect it like we protect our own personal information. Recent publicity over the theft of Sony PSN data underscores both the economic and ethical importance of protecting personal data.
This editorial was originally published on Feb 17, 2006. Steve is traveling in the UK this week and we are re-printing some old pieces. This one talks about a search engine for code.
Fabiano Amorim was asked a couple of questions about SQL Server Distribution Statistics. Having given an answer based on his current knowledge, he then decided to find out for himself whether what he'd said was right, and started an epic journey of exploration into Distribution Statistics and the way that the Query Optimiser uses them.
This editorial was originally published on Jan 9, 2006. Steve is traveling to the UK this week and we are reprinting a few older editorials. This editorial talks about the health of your eyes, a topic of concern for those of us that work with computers regularly.
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