Upserts in Amazon Redshift
This article discusses different approaches of Upserts (update+inserts) in Amazon Redshift
This article discusses different approaches of Upserts (update+inserts) in Amazon Redshift
Preparations for Summit 2023 are fully underway! We thought what better way to introduce you to some of this year’s sponsors than sit down with them and find out what they have in store for you in November…
One of the more challenging technical details of columnstore indexes that regularly gets attention is the need for data to be ordered to allow for segment elimination. In a non-clustered columnstore index, data order is automatically applied based on the order of the underlying rowstore data. In a clustered columnstore index, though, data order is not enforced by any SQL Server process. This leaves managing data order to us, which may or may not be an easy task.
Secure your Sponsorship package before the rates go up. PASS Data Community Summit 2023 is where the database community meets every year to make life-long connections with peers, network with industry leaders, and advance their careers. With over 170 technical sessions, and a great line-up of sponsors, this is your time to secure your space before August 30 and get a preferred booth location.
Microsoft Fabric changes the paradigm for how you might store data in your warehouse.
The most common method on the internet for combining DATE and TIME columns in SQL Server is incorrect. This article demonstrates why that and other methods are incorrect and two lesser known high performance methods that produce correct results even for the "edge cases".
Are you looking to modernize and migrate your data but have questions about the complex organizational challenges? We recently hosted the webinar: Overcoming Organizational Challenges in Data Modernization and Cloud Migration: A Guide for Senior IT Leaders. This blog post summarizes the conversation into 7 key points.
This article employs Power Query features to combine queries and implement requirements in different listed scenarios.
Last week I was able to attend THAT conference in Wisconsin Dells, Wisconsin. It was my first time in the great state of cheese, and the conference lived up to its reputation. As a developer focused conference (rather than a database conference), I didn't have much expectation that my session about automating database changes would […]
Learn how you can use AutomatedLab to quickly create new environments.
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