A Fine Slice Of SQL Server
This update introduces several enhancements to native incremental copy and change data capture (CDC) capabilities in Copy job, including support for additional data source stores for incremental copy, expanded CDC support for SAP Datasphere Outbound for Amazon S3 and Google Cloud Storage (in addition to Microsoft Cloud Storage), and Column Mapping support for CDC in Copy job.
Click through to see what has changed in the copy job.
Leave a CommentI haven’t participated in a #TSQL Tuesday in quite some time. I saw this topic and said, “That’s perfect!” I love talking about Failure and mistakes! I have a whole presentation about it, and I’m hoping to make a series of blog posts about it very soon.
You do not learn from success in life; you learn from failure. I hope you are making lots of mistakes so that you can learn!
Read on for a story from Pat around creating a trigger and not realizing the consequences. This is why we don’t let just anybody have mogwais triggers.
Elizabeth Christensen lays out an argument:
Lots of us started with a Postgres database that incremented with an id
SERIAL PRIMARY KEY. This was the Postgres standard for many years for data columns that auto incremented. The SERIAL is a shorthand for an integer data type that is automatically incremented. However as your data grows in size,SERIALs andINTs can run the risk of an integer overflow as they get closer to 2 Billion uses.We covered a lot of this in a blog post The Integer at the End of the Universe: Integer Overflow in Postgres a few years ago. Since that was published we’ve helped a number of customers with this problem and I wanted to refresh the ideas and include some troubleshooting steps that can be helpful. I also think that
BIGINTis more cost effective than folks realize.
Click through for Elizabeth’s argument. I’d say that this is very similar for SQL Server, where I’m more inclined to create a BIGINT identity column, especially because I almost automatically apply page-level compression to tables so there’s not really a downside to doing this. Identity columns don’t have a domain, so there’s no domain-specific information like you’d get with a column such as Age; and with page-level compression, you’re not wasting space.
Leave a CommentUmair Shahid digs into the arguments for and against:
“Should PostgreSQL run on Kubernetes too?”
The worst answers are the confident ones:
- “Yes, because everything else is on Kubernetes.”
- “No, because databases are special.”
Both are lazy. The right answer depends on what you’re optimizing for: delivery velocity, platform consistency, latency predictability, operational risk, compliance constraints, and, most importantly, who is on-call when things go sideways.
Click through for a detailed analysis. It’s a similar story in SQL Server:
Leave a CommentBrent Ozar notes some problems:
SQL Server 2025 Cumulative Update 1 came out last week, and I was kinda confused by the release notes. They described a couple dozen fixed issues, and the list seemed really short for a CU1.
However, the more I dug into it, the weirder things got. For example, there were several new DMVs added – which is normally a pretty big deal, something to be celebrated in the release notes – but they weren’t mentioned in the release notes. One of the DMVs wasn’t even documented. So I didn’t blog to tell you about CU1, dear reader, because something about it seemed fishy.
Read on for a big deal.
Leave a CommentJohn Cook defends (some) ugly code:
Ugly code may be very valuable, depending on why it’s ugly. I’m not saying that it’s good for code to be ugly, but that code that is already ugly may be valuable.
That something is ugly is typically a visceral reaction. But I try to tease out why I think code is ugly, as it can be for several reasons.
Younger me was all about rewriting and removing nasty, inefficient, ugly code. But older me realizes that only some nasty, inefficient, ugly code is actually bad. I still will heartily argue that code is a liability and that most code bases could make do with a spring cleaning. But it has to come from a place of understanding first. I have a lot more on the topic of technical debt in an essay I wrote a few years ago. And I did purposefully cut myself off at one point to be cute.
Leave a CommentChris Webb breaks out the stopwatch:
Carrying on my series on troubleshooting Power BI performance problems with Performance Analyzer, another situation where a report may be slow even when the DAX queries it generates against the underlying semantic model are fast is when you have large images displayed in an Image visual. Let’s see an example.
Click through for that example. And maybe don’t plop in so many 25 MB images.
Leave a CommentAkhil Reddy Banappagari performs a comparison:
Choosing a correct datatype mapping while migrating from Oracle to PostgreSQL is very important to avoid migration failures. Especially when we have date and time involved, it is very important to understand the behavior in both Oracle and PostgreSQL. In this article, we are going to discuss about DATE datatype in Oracle and PostgreSQL, and avoiding constraint violations while migrating from Oracle to PostgreSQL when DATE data type is involved.
I’d consider this a case where Oracle is the weird one.
Leave a CommentKoen Verbeeck comes in with a public service announcement:
I’m not trying to start up a debate whether you should use tabs or spaces when indenting code. Personally, I prefer spaces because when I copy the code to another editor the outlining of the code remains the same while with tabs it’s not always the case (looking at you, Word and Outlook). But I don’t want to hit the spacebar 4 times whenever I want to indent something, so I use the setting “insert spaces instead of tabs”:
Click through for a situation in which that might not happen correctly, as well as what you can do about it.
Leave a CommentSebastiao Pereira tries to preserve privacy:
Homomorphic encryption is a cryptographic algorithm that lets computations be performed directly on encrypted data without needing to decrypt it. This enables secure outsourcing of computations on sensitive data while preserving privacy.
Is it possible to have homomorphic encryption in SQL Server?
There’s a lot of effort and a CLR module involved, but it is possible. Now, my next question is, how well does it perform in practice? 10 patients is fine for a demonstration, but at what point does this tip over?
Leave a Comment