Operations | Monitoring | ITSM | DevOps | Cloud

Code Compare 5.5 R1 Adds Integration Support for Visual Studio 2026

We’re excited to share Code Compare 5.5 R1, the latest update to our code comparison and merge tool. This release adds integration support for Visual Studio 2026, so teams can compare changes and resolve merge conflicts directly within the IDE workflow they already use. With Code Compare 5.5 R1, developers can review differences, apply merges, and handle conflicts in Visual Studio 2026 using the same comparison experience they rely on across projects and repositories.

Counting Consecutive Repeating Segments in URL Strings via Trino SQL

Short Summary: Sometimes URL paths repeat by mistake because of tracking problems or redirect loops.. In this guide, you’ll learn how to find and count those repeats using Trino SQL. By using simple SQL tools like CTEs, arrays, and window functions, you can break a long link into smaller pieces and clean up the data without using complex regex.

Optimizing PostgreSQL Performance for Large Tables with Boolean Filters

Short Summary: In this guide, we address performance problems that occur when PostgreSQL queries very large tables containing low-cardinality boolean fields. It also demonstrates how composite indexes, created and tested with Devart tools, allow PostgreSQL to locate the required rows directly instead of scanning the entire table.

Scaling Your CLI Query Tool: Prioritizing Database Support for Maximum Impact

Short Summary: This article explains how to expand your CLI query tool so it can handle multiple databases. First, we focus on key relational systems, then move to data warehouses. We’ll use dbForge Edge as a reference point, showing how different databases can be managed in one place while keeping automation simple.

Choose the Right SQLite ODBC Driver: Practical Comparison for 2026

Picking an SQLite ODBC driver is like choosing a key; you need one that opens every door cleanly, without snapping or jamming. The right driver must connect your data effortlessly—no errors, no limitations. It also has to withstand real challenges: complex queries, cross-platform environments, and large datasets. In this guide, we’ll show you which 2026 drivers stand up to these demands, so you can pick the one that won’t let you down.

Solving the Cartesian Count Problem: Efficient Multi-Table Aggregation in Complex Databases

Short Summary: Counting related records across multiple dependent tables can produce wrong totals or slow queries when standard joins are used. This article explains a more reliable way to do this by counting each table separately, applying date filters, and checking that the query still runs well on large datasets. Tools such as dbForge Edge can also help if needed.

Mastering Cross-Database Date Manipulation: Subtracting Days in MySQL and H2

Short Summary: Different databases use different SQL syntax for simple tasks like subtracting days from a date. In this post, we show how these differences appear across databases such as MySQL, PostgreSQL, SQL Server, Oracle, and H2. We also explain how dbForge Edge helps teams work with them in one place while keeping application logic consistent.

ODBC Driver for MySQL: Open-Source vs Commercial (2026)

The MySQL ODBC driver is what keeps BI tools, reporting systems, and ETL pipelines connected to MySQL without errors. Teams have depended on it for years, and it’s still vital today, especially with MySQL ranked worldwide in February 2026. However, not all ODBC drivers are built alike. There are two categories: open-source options and commercial ones. While both connect applications to MySQL, they differ in areas like stability, performance, security, and support.

Mastering Temporal LEFT OUTER JOINs for Historical State Analysis in SQL Server

Short Summary: This guide shows how to use time-based LEFT OUTER JOINs with SQL Server temporal tables, step by step. You’ll see how dbForge tools help you fine-tune these queries so you can get accurate reports for specific points in time, fully understand how your data changes, and confirm that your logic is correct.