Operations | Monitoring | ITSM | DevOps | Cloud

We are excited to announce the release of SSIS components Data Flow Components version 4.0, an update that delivers expanded compatibility with the latest development tools and database platforms. Version 4.0 introduces full support for Visual Studio 2026 and Visual Studio 2026 Insiders, ensuring developers can seamlessly adopt Microsoft’s newest IDE while continuing to work with familiar workflows.

Tempo 2.10 has arrived, delivering TraceQL enhancements, improved cardinality management for the metrics-generator, vParquet5, and more. You can continue reading and check out the video below to learn more about these and other new features. The Tempo 2.10 release notes and changelog provide more in-depth details and include all of the changes that came with this release.

In PostgreSQL, the EXPLAIN ANALYZE statement gives you a detailed report of what actually happens when you execute a query. This kind of information is important for troubleshooting slow queries, but using EXPLAIN ANALYZE to collect this data is often challenging in a production environment. Datadog Database Monitoring now supports automatic collection of EXPLAIN ANALYZE plans for PostgreSQL, enabling you to easily capture execution details that help you troubleshoot slow queries.

DataReader and DataSet are two significant data access models that can greatly impact the performance, scalability, and responsiveness of your.NET application. The connected model, powered by DataReader, keeps a live connection open and streams data forward-only to maximize speed and minimize memory usage. The disconnected model, implemented through DataSet, takes the opposite approach. It loads data into memory so you can edit and reuse it without constant database interaction.

PostgreSQL AI is gaining attention as SQL complexity increases in production environments. It addresses a common problem: extended queries that accumulate joins, nested logic, and edge cases. Without AI assistance, these queries are often harder to write and review, driving 20–40% of developer time into debugging. In practice, these challenges affect PostgreSQL users in different ways.

HubSpot QuickBooks integration is now a core operational requirement as data silos continue to disrupt workflows across 82% of enterprises. It addresses a critical failure point between CRM and accounting, where disconnected systems fragment customer, invoice, and revenue data. In practice, this separation often leads to duplicated customer data, invoice corrections, and revenue reports that lag behind real activity.

Now, we will explore how this foundational strength translates into organizational maturity and lay out the durable operating habits required to bridge the gap between reactive firefighting and strategic performance engineering.

VictoriaMetrics is a fast, cost-efficient, and highly scalable time-series database designed as a drop-in replacement for Prometheus storage. It is widely used for collecting, storing, and querying metrics at scale, while remaining lightweight enough to run as a single binary or container. Because it is fully Prometheus-compatible, VictoriaMetrics supports standard PromQL queries and integrates seamlessly with Grafana.

Redgate Flyway’s January update brings faster drift resolution, AI-powered deployment descriptions, and a look back at everything we shipped in 2025. Plus, we want to hear from you about how you’re managing database changes.

This post covers ~80% of VictoriaLogs concepts and features people ask about most often. For deeper details and full references, see the official VictoriaLogs documentation. Part of a series.

SQL Prompt’s January release brings support for Microsoft Fabric and an exciting new preview feature.

As the new year begins, development teams are looking to build momentum, set clear goals, and establish reliable, scalable processes that will help them deliver value consistently throughout 2026. That’s why many teams are turning to SQL Toolbelt Essentials: a powerful, easy-to-adopt toolkit that helps teams speed up database development, reduce risk, and standardize workflows.

2025 has been quite a year! As we enter into 2026, we want to share all the great features that VictoriaMetrics Cloud has brought in the last quarter. Remember that this Quarterly Live Update is available in video format as well here: Let’s get to it!

First, I’d like to say how happy and lucky I feel to be working at Redgate on Flyway. I’m one of two Senior Product Managers in Flyway and we’ve been looking for a third to join us. We work alongside the Flyway Group Leadership Team (Group Product Manager, Architect, Lead Designer, and Development Manager) and four amazing engineering teams with embedded designers. We also work with the Product Support, Marketing, Sales, and Customer Success teams.

Teams work on databases across multiple environments (e.g., Development, Test, QA/UAT, Production) and differences can happen in these databases over time. A hot fix applied directly to Production or a quick change applied in Test while troubleshooting are examples of how the schema can diverge from what’s expected. These differences are known as drift and can cause problems with deployments making them unpredictable and harder to troubleshoot.

Redis is a widely used in-memory data store, commonly deployed as a cache, session store, message broker, or fast key-value database. Because Redis often sits on the critical path of an application, having visibility into its behavior (memory usage, client connections, command throughput, cache efficiency) is essential for troubleshooting and performance tuning.

AI-powered coding assistants have transformed how developers write software. Tools like Claude Code, OpenAI Codex, Gemini CLI, Qwen Code, and OpenCode have introduced what many call “vibe coding” — a new paradigm where users describe their intent and AI agents handle the implementation details. But as these tools become integral to development workflows, a critical question emerges: how do we understand what’s happening under the hood?

Prior to working for a software company, I spent most of my career working for financial organizations. I have lots of friends who still do. Talking with one the other day, the question came up, what keeps you up at night? Her one word response was a little surprising: Fraud. Understand, she’s in charge of managing data at a bank. You’d expect maybe uptime, performance, high availability, any of the standard data management worries. Instead, it’s fraud.

InfluxDB is a widely used time-series database designed for storing and querying metrics, events, and telemetry data. It’s commonly used for infrastructure monitoring, application instrumentation, and IoT-style workloads where time-based data is central. In many environments, InfluxDB already exists as part of the monitoring or data collection pipeline, and the primary need is simply to visualize that data effectively.

TINYINT is one of the simplest numeric data types you can ever work with in SQL databases. It stores small numeric values, saves space, and is commonly used for flags, statuses, and boolean-like fields. But the moment you bring C# into the picture, things get intriguing. There is no TINYINT keyword in C#, and no one-to-one mapping you can use. Instead, you are left asking an important question: What is the correct C# equivalent of the TINYINT data type in SQL?

HubSpot Slack integration has become essential for the 238,000 companies on HubSpot and the 42 million users active on Slack each day. However, the native connector offers only limited functionality. Notifications often get buried, CRM updates remain locked inside HubSpot, and reporting still relies on manual exports. Worse, it lacks workflow customization and bidirectional updates leaving teams without the visibility and flexibility they need. This guide shows how to move past those limits.