An Introduction to GitHub for DBAs
Distributed source control is really intimidating: branches, pull requests, merges – will somebody just take my code, for crying out loud? Why does it have to be so complicated and involved?
Distributed source control is really intimidating: branches, pull requests, merges – will somebody just take my code, for crying out loud? Why does it have to be so complicated and involved?
No matter what the reason you have sensitive information, you need to treat it carefully.
Most organizations today understand the value of analysing their data. In some cases, they haven’t realized the value or are just getting started. This article, by Data Platform MVP Gogula Aryalingam, describes how analytics can start small – with just one Power BI dashboard – and grow from there.
This article will help with gaining confidence and familiarity with Microsoft Azure's Data Lake Analytics offering to process large datasets quickly while demonstrating the potential and capabilities of U-SQL to aggregate and process big data files.
Steve talks about the level of engineering effort we need in software development.
Triggers can be confusing and complex for many developers new to SQL. Steve Jones gives a few ideas for learning more about this construct as well as practicing writing them.
If a picture paints a thousand words then can GDPR regulation be represented in diagram form? Could doing so make it easier to comply with the regulation by making it easier to understand?
Today we have a guest editorial from Andy Warren as Steve is away on vacation. This was originally published on Dec 23, 2014. I was reflecting recently on my first real IT job. It was a small-ish company when I joined it, perhaps a hundred employees or so, and still using a mishmash of software […]
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