Another Way to Look at Trees
An alternative to tree traversal, and ultimately more efficient way to look at organizational structures is presented.
An alternative to tree traversal, and ultimately more efficient way to look at organizational structures is presented.
There is a paradox in the nature of the abstractions that many developers want when dealing with databases. They will strain at the gnat, but swallow a camel (Matthew 23:24). Whereas they will recoil with horror when a DBA suggests that an abstraction layer based on views, functions and procedures in a separate database schema […]
What should a good DBA do? Steve Jones came across a list he likes that showcases those things that should guide your efforts on a daily basis.
Using online accounts for license management has some advantages, Red Gate is researching how to implement this for our tools in a way that improves the experience for all involved. To say thank you for your participation, there's a chance to win a $25 Amazon certificate.
Continuous Integration and automatic builds are fantastic tools for software teams, but only if developers take responsibility for their code. Karsten Kempe explains how to use Team Foundation Server to drive better continuous integration, and walks through a simple open-source tool he built to make nightly builds more transparent, and more valuable.
Steve Jones asks about what you might change about yourself at work for this Friday's poll.
Splitting strings based on patterns supported by LIKE and PATINDEX can be an interesting way to address a wide variety of problems.
For many developers, does DBA really stand for Don't Bother Asking? David Poole thinks it is time to end the unnecessary conflict between developer and DBA, and explains how to deal professionally with the inevitable friction between development and operation activities in IT.
There's a new contest going on, giving you the chance to win some software, SQL training, and a vacation, all at once.
This article summarizes the factors to consider and provide an overview of various options for HA and DR in cloud based SQL Server deployments.
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...
Hi All I am trying to find 'bad' characters that users might type in....
WhatsApp: 0817839777 Kw. Industri Pulogadung, Jl. Raya Bekasi Km. 21, Ruko No.A2/18-19, RW.3, Wil,...
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