I posted last time that I'd completed my Part 1 eBook on Core Concepts. The Part 2 eBook is on the differences in the SQL language between Snowflake and SQL Server.
This next series of blog posts will focus on the query language, particularly on DML (data manipulation language). DDL (data definition language i.e. CREATE, ALTER, DROP) differences will be covered in the Part 3 series on administration.
Snowflake has quite a rich SQL language but it's quite different to the T-SQL offered by SQL Server in many ways. I'm planning to work right through the Snowflake SQL language documentation and try everything in it, so you don't have to.
In this series of posts though, I'll look primarily at what's different, not on what's the same. (Detailed coverage of the language itself will be in our upcoming online course on Snowflake SQL. It's being built now).
This post will serve as an index to the other posts in this series.
You'll find the other posts in the list below:
Part 1: Sequences: The good and the not so good
2 thoughts on “Snowflake SQL for SQL Server Users – SQL Language Differences”
Greg – thank you for the free Part1 ebook and thank you for putting together this list of SQL Language differences. It is something very much needed as I find myself thrown into learning Snowflake. If you want some suggestions or some guest posts on this let me know. I find something interesting about once a week that makes me go, "huh? wonder why they did it that way" Researching Sequences and Identity were how I found your blog (this month)
Hi Mike, you are most welcome. I've been tied up way too much the last couple of weeks, and am looking at migrating a bunch of our samples, tools, etc. to Snowflake. Most of the discussions will come from what we learn on that but always happy to get suggestions.
As for sequences, I'm not sure how on earth you're meant to use them in Snowflake really. Without a way to change the next value to be issued, they really aren't very useful.