The database stories enterprise IT leaders actually read.
Volume 342, Issue 2 · 6 articles from 4 issues
An overview of MySQL, the free open-source relational database, covering features, licensing, platforms, and installation.
This Analytics Insight download-hub guide describes MySQL as an open-source relational database management system that uses SQL to store and manage structured data.
The Community Edition is free under the GPL and runs on Windows, Linux, macOS, and other Unix-like systems, with Community Server 8.0.46 listed among current releases.
The guide highlights InnoDB transactions, replication, Group Replication, InnoDB Cluster, indexes, views, stored procedures, and triggers. It also outlines system requirements and basic setup steps, and notes commercial editions for businesses needing extra features and support.
TiDB CTO Ed Huang says AI agents now create most new databases, requiring serverless, branchable, scale-to-zero architectures.
In this interview, TiDB co-founder and CTO Ed Huang argues database scalability is largely solved and the new frontier is architectural simplification for AI agents. He says over 90% of new TiDB Cloud clusters are created by AI agents, which spin up, mutate, and discard databases at machine speed.
Huang lists requirements including second-level provisioning, S3-backed compute-storage separation, non-blocking schema changes, unified transactional, analytical, and vector workloads, and native branching.
He also calls for cost governance through scale-to-zero, request-unit billing, and per-agent metering that acts as a circuit breaker.
Percona survey finds 97% of US DBAs run end-of-life database versions, citing upgrade risk and cost pressures.
Percona's 2026 State of Open Source Database Management Report found that 97% of US-based DBAs still run database versions past official end-of-life.
Upgrades are treated as risky cross-stack migrations involving legacy dependencies, deprecated features, client compatibility, and changed defaults, such as MySQL 8.0's authentication changes.
Cost pressures were the top obstacle, with cloud consumption costs (31%) ahead of licensing (23%), while 54% said vendor lock-in hampers regulatory adaptation.
For AI readiness, fragmented data architecture and skills shortages tied as top barriers at 23% each, and unsupported software raises growing security concerns.
Combining graph databases with vector search reduces hallucinations and doubles factual accuracy on complex questions.
Neo4j highlights research showing that integrating graph-based knowledge retrieval with vector RAG significantly improves LLM accuracy.
Testing across 510 complex questions found vector-plus-graph RAG achieved more than twice the precision and recall of vector-only approaches while reducing hallucinated content. The study demonstrates that structured knowledge graphs enable the multi-hop reasoning that sophisticated queries require.
The practical implication is that graph-augmented retrieval makes AI systems more trustworthy for real-world applications.
PostgreSQL 19 adds SQL/PGQ property graph syntax, reducing the need for a separate graph database in some workloads.
PostgreSQL 19 gains standardized graph query capability via SQL/PGQ, the property graph syntax added to the official SQL standard in 2023 with heavy input from OpenCypher engineers.
The baked-in syntax lets teams query property graphs directly and can remove the need for a separate graph database in some scenarios.
The Register frames the work as one of the significant multi-vendor collaborations in the PostgreSQL ecosystem, involving major contributors and SQL standards committee members.
Execution performance is reported as good for many workloads, though indexing add-ons still need to catch up in subsequent releases. The article situates the feature against PostgreSQL's rise to the most popular database among developers.
PostgreSQL remains capable, but enterprise AI demands integrated governance that extensions may not deliver.
While PostgreSQL is a strong open-source relational database, the shift toward agentic AI raises questions about data governance, security and operational complexity that a collection of extensions and services may not adequately address.
Oracle AI Database 26ai argues for a converged architecture keeping vectors, transactions and governance unified. The real evaluation should focus on total cost of ownership, data movement requirements and consistency of security policy across data types, rather than feature checklists or licensing cost alone.