If you’re getting SQL Server error 8110 that reads “Cannot add multiple PRIMARY KEY constraints to table…” it’s because you’re trying to add more than one primary key to a table. In SQL Server, a table cannot contain more than one primary key.
It’s quite possible you were trying to create a composite primary key, and so you might need to fix your syntax. If that’s the case, read on.
Data lineage is one of those concepts that sounds more complicated than it is. Once you understand the basic idea, it’s actually pretty intuitive. And it solves a problem that anyone who works with data has run into.
Data lake is one of those terms that gets thrown around a lot in conversations about data strategy, often alongside data warehouses and data marts. But what actually is a data lake, and how does it fit into the picture? Let’s find out.
SQL Server 2025 ships with a handful of genuinely useful additions, and JSON_OBJECTAGG() is one of the better ones. It lets you aggregate rows into a single JSON object (with key-value pairs pulled directly from your data) without any string hacking or FOR JSON PATH gymnastics.
Here’s what it does, how it works, and when you might actually use it.
Data doesn’t always arrive clean, structured, or ready to use. And anyone who’s worked with data knows that gap between raw information and actionable insight is where a lot of the real work happens. ELT is a modern approach to bridging that gap.
Unlike its older cousin ETL, ELT flips the script by loading data into its destination first and transforming it there, taking advantage of the processing power that today’s cloud data warehouses have in abundance. The result is a faster, more flexible pipeline that’s become something of a default choice for many data teams building on platforms like Snowflake, BigQuery, or Redshift.
If you’re getting SQL Server error 13680 that reads something like “Column ‘details’ on table ‘table_name’ is not of JSON data type, which is required to create a JSON index on it.” it looks like you’re trying to create a JSON index on a non-JSON column. You can only create JSON indexes on columns defined with the JSON type.
To fix this issue, be sure that the column is of JSON type before running CREATE JSON INDEX on it.
If you’ve spent any time around data teams or analytics tools, you’ve probably heard the term ETL thrown around. It sounds technical, but the concept is actually pretty straightforward. This article looks at what the term actually means, how it works, and why it matters.
A time series database (TSDB) is a database built specifically to store and query data that’s tied to timestamps. This could include things like sensor readings, stock prices, server metrics, or IoT data. Basically anything where the when is just as important as the what.
Standard relational databases can technically store this kind of data, but they weren’t designed for it. Time series databases are optimized from the ground up for time-ordered data, which means they’re faster, more efficient, and more practical for time-heavy workloads.
In SQL Server, Query Store configuration settings can be adjusted after it’s been enabled to better suit your database’s workload and performance requirements. You might need to increase storage limits, change capture modes, or adjust data retention policies as your needs evolve.
If you’re getting SQL Server error 13681 that states “A JSON index already exists on column…” , it’s probably because you’re trying to create a JSON index on a column that already has one. In SQL Server, each JSON column can have no more than one JSON index.
The solution here is to simply stop trying to create a second JSON index. Another option would be to drop the existing one and create the new one.