Daniel Mills
Current Organizations / Institutes
The organizations/institutes from the scholar's latest article
Research Interests
Daniel Mills has a total of 31 co-authors. Here are the top co-authors by number of shared publications:
- Boyuan Zhang
Snowflake, Bellevue, WA, USA
2 shared publications - Daniel Sotolongo
Snowflake, Bellevue, WA, USA
2 shared publications - Dzmitry Pauliukevich
Snowflake, Berlin, Germany
2 shared publications - Niklas Semmler
Snowflake, Berlin, Germany
2 shared publications - Sasha Lionheart
Snowflake, Bellevue, WA, USA
2 shared publications - Tyler Akidau
Snowflake, Bellevue, WA, USA
2 shared publications
Latest Publications
- Open Access
- 22 June 2025
- Published by Association for Computing Machinery (ACM)
- p. 622-634
Streaming Democratized: Ease Across the Latency Spectrum with Delayed View Semantics and Snowflake Dynamic Tables
- 22 June 2025
- Published by Association for Computing Machinery (ACM)
- p. 622-634
Open AccessStreaming Democratized: Ease Across the Latency Spectrum with Delayed View Semantics and Snowflake Dynamic Tables
- Open Access
- 13 June 2023
- Published by Association for Computing Machinery (ACM) in Proceedings of the ACM on Management of Data
- Vol. 1 (2) , 1-27
What's the Difference? Incremental Processing with Change Queries in Snowflake
Incremental algorithms are the heart and soul of stream processing. Low latency results depend on the ability to react to the subset of changes in a dataset over time rather than reprocessing the entirety of a dataset as it evolves. But while the SQL language is well suited for representing streams of changes (via tables) and their application to tables over time (via DML), it entirely lacks a method to query the changes to a table or view in the first place. In this paper, we present CHANGES queries and STREAM objects, Snowflake's primitives for querying and consuming incremental changes to table objects over time. CHANGES queries and STREAMs have been in use within Snowflake for three years, and see broad adoption across our customers. We describe the semantics of these primitives, discuss the implementation challenges, present an analysis of their usage at Snowflake, and contrast with other offerings.
- 13 June 2023
- Published by Association for Computing Machinery (ACM) in Proceedings of the ACM on Management of Data
- Vol. 1 (2) , 1-27
Open AccessWhat's the Difference? Incremental Processing with Change Queries in Snowflake
Incremental algorithms are the heart and soul of stream processing. Low latency results depend on the ability to react to the subset of changes in a dataset over time rather than reprocessing the entirety of a dataset as it evolves. But while the SQL language is well suited for representing streams of changes (via tables) and their application to tables over time (via DML), it entirely lacks a method to query the changes to a table or view in the first place. In this paper, we present CHANGES queries and STREAM objects, Snowflake's primitives for querying and consuming incremental changes to table objects over time. CHANGES queries and STREAMs have been in use within Snowflake for three years, and see broad adoption across our customers. We describe the semantics of these primitives, discuss the implementation challenges, present an analysis of their usage at Snowflake, and contrast with other offerings.