Explore >> Select a destination
|
You are here 
|
boringsql.com | ||
| | | | |
jack-vanlightly.com
|
|
| | | | | In the previous post, I covered append-only tables, a common table type in analytics used often for ingesting data into a data lake or modeling streams between stream processor jobs. I had promised to cover native support for changelog streams, aka change data capture (CDC), but before I do so, I think we should first look at how the table formats support the ingestion of data with row-level operations (insert, update, delete) rather than query-level operations that are commonly used in SQL batch commands. | |
| | | | |
janko.io
|
|
| | | | | At work I was tasked to migrate our time-series analytics data from CSV file dumps that we've been feeding into Power BI to a dedicated database. Our Rails app's primary database is currently MariaDB, but we wanted to have our analytics data in a separate database either way, so this was a good opportunity to use Postgres which we're most comfortable with anyway. | |
| | | | |
brunoscheufler.com
|
|
| | | | | In addition to the classic INSERT and UPDATE operations, there's another powerful data-modification technique, called upserting. Combining INSERTs for non-existing records and UPDATEs for existing ones, upserts enable various use cases to ensure a document exists and is modified accordingly, if it was created earlier, all while maintaining a concurrency-safe and atomic behavior.... | |
| | | | |
callihandata.com
|
|
| | | This month's T-SQL Tuesday topic comes from Matthew McGiffen, who asks us to talk about encryption and protecting data in SQL Server. To read the full topic invite, click the T-SQL Tuesday logo to the right. For this month's invite, I thought I'd write about Transparent Data Encryption (TDE) and give a reminder about how... | ||
