October 2026 Summaries

4 posts from Tessell

Filter
Month: Year:
Post Summaries Back to Blog
Tessell announced at Oracle CloudWorld on October 23, 2026, that it is introducing Agentic Database Lifecycle Management through three specialized agents built with Google’s Gemini for enterprise database workloads on Google Cloud. The Ops Agent automates administration tasks such as provisioning, monitoring, recovery, scaling, credential rotation, and deployment; the Governance Agent manages security, compliance, backup, disaster recovery, encryption, access controls, and data masking; and the Migrate Agent supports estate discovery, target planning, migration runbooks, replication monitoring, and database modernization. The agents enable DBAs, SREs, platform owners, and migration teams to manage engines including Oracle, SQL Server, PostgreSQL, MySQL, MongoDB, and Milvus through natural-language conversations, while routing infrastructure operations to Google Cloud compute and storage services. Tessell, a multi-cloud DBaaS platform operating in customers’ own cloud accounts and encryption environments, said the agents would be demonstrated at the event and made available to enterprise preview customers during the quarter.
Oct 23, 2026 1,115 words in the original blog post.
Tessell presents a multi-cloud database management platform for Oracle, SQL Server, PostgreSQL, and MySQL that emphasizes customer-controlled security, automated lifecycle operations, high availability, governance, and cost reduction across AWS, Google Cloud, and Azure. Its featured migration case describes moving an active Oracle SE2 database supporting ingestion, reporting, and billing from on-premises Windows to Linux on Google Cloud with minimal disruption. Because Transportable Tablespaces would require lengthy downtime for datafile conversion and Enterprise Edition features such as GoldenGate were unavailable, the team used a full RMAN backup and restore followed by automated archive-log shipping and recovery roughly every 30 minutes. Scripts standardized the restore, recovery, activation, and validation stages, leaving only final log application and database activation for the cutover window, which reduced downtime from potentially hours to minutes. The approach depends on reliable archive-log retention, coordination of structural database changes during migration, and acceptance that rollback requires returning to the original source system.
Oct 22, 2026 2,000 words in the original blog post.
Tessell Chief Strategy Officer Jeff Carter and presales leader Tim Davis examine database-estate costs as a combination of infrastructure spending, security risk, and operational effort, arguing that one-database-per-VM deployments can leave many low-traffic systems underutilized and suitable for consolidation. They cite Tessell customer examples and claims of cloud-cost reductions through higher server utilization, while emphasizing that consolidation should preserve hardware, licensing, and failure-domain considerations. The discussion also addresses AI development’s demand for current production-like data, warning that slow governed provisioning can lead developers to create untracked copies, and recommending auditable self-service access, least-privilege controls, row- and column-level security, and masked, expiring clones. AI’s role is described across data access for models, built-in database-engine capabilities such as tuning and autoscaling, and automation in a management control plane for provisioning, patching, backups, failover, and compliance. Although routine database operations are expected to become increasingly automated, the authors contend that DBAs will remain important for data interpretation, performance optimization, and oversight of business-critical systems.
Oct 16, 2026 2,402 words in the original blog post.
Tessell presents its multi-cloud database platform as a way to manage Oracle, SQL Server, PostgreSQL, MySQL, and other database workloads across AWS, Google Cloud, and Azure with automated provisioning, lifecycle operations, security controls, high availability, disaster recovery, cost visibility, and data governance. In the first of a three-part series, Chief Strategy Officer Jeff Carter argues that conventional cloud migrations can create a “cloud performance trap,” in which organizations must purchase larger compute instances to obtain needed storage IOPS, thereby increasing core-based Oracle and SQL Server licensing costs, especially for high-availability deployments. He says Tessell’s NVMe-backed architecture separates storage performance from compute sizing while preserving durability through synchronization and logging, allowing high IOPS without scaling CPU capacity. The piece also contends that manually managed transactional databases can limit real-time AI and RAG applications because unpredictable agent queries may disrupt production systems; it recommends persistent, continuously synchronized read replicas using native database replication or change data capture to provide current operational data without placing AI workloads on primary databases.
Oct 05, 2026 2,639 words in the original blog post.