← CoreEdge Dynamics products
Data intelligence · AI-assisted SQL engineering

Core SQL Engineer: Analyze Databases, Generate SQL, and Troubleshoot Production—Safely.

Core SQL Engineer is an AI assistant for SQL Server work: natural-language and screenshot-to-SQL generation, schema analysis, query optimization, index recommendations, execution-plan review, and production diagnostics.

Its strongest capability is safe operation on real environments. Read-only by default, guardrails and validation before every run, and full auditing — safe for an analyst, honest for a DBA at 2 a.m.

From a plain-language question to a blocking-chain root cause, it works the way the people who own the database actually work.

Start a conversation

Natural language in, working SQL out

Screenshot → SQL

Paste a screenshot of a table, report, dashboard, or expected output. Core SQL Engineer infers the required columns, filters, grouping, and sorting, compares against your schema metadata, and reconstructs a probable query — explaining every assumption it made along the way.

Screenshot-to-SQL is assisted reconstruction, not guaranteed recovery of the original query.

It actually knows your database

Core SQL Engineer reads database metadata — tables, columns, keys, indexes, views, stored procedures, and functions — and builds a semantic representation of the schema: candidate join paths, unclear or missing relationships, duplicated structures. It can generate schema summaries and data dictionaries, and explain an unfamiliar database to a new team member.

Performance: plans, indexes, and the smallest effective fix

Query & plan analysis

  • Execution-plan review — graphical or XML
  • Table scans, key lookups, expensive sorts & hash operations
  • Poor cardinality estimates & parameter-sniffing symptoms
  • Implicit conversions & non-SARGable predicates
  • Scalar-function bottlenecks, spills, memory-grant issues
  • Estimated-vs-actual row differences, warnings, row-goal effects
  • Root-cause summary and the smallest effective correction

Index analysis

  • Missing-index opportunities — with healthy skepticism toward raw DMV suggestions
  • Unused, duplicate & overlapping indexes
  • Composite and filtered index recommendations
  • Included-column and index-width review
  • Write-versus-read trade-off analysis
  • Fragmentation and maintenance-cost review
  • CREATE / DROP / consolidation scripts with expected impact

Production troubleshooting at 2 a.m.

Blocking chains, deadlock graphs, wait stats, active sessions, long-running queries, CPU / memory / I/O pressure, tempdb, transaction-log growth, connection pressure, job failures, statistics health, Query Store regressions, and plan-change detection — walked to a root cause with a prioritized fix.

Diagnostics draw on SQL Server's own instrumentation: DMVs (sys.dm_exec_requests, sys.dm_os_wait_stats, sys.dm_tran_locks, index and missing-index DMVs), Query Store, Extended Events, deadlock XML, SQL Agent history, and file / tempdb / log metadata. The exact set depends on the SQL Server version and granted permissions.

Database health assessments

Configuration, file layout, backups, recovery model, integrity checks, growth, security and permissions, index and statistics health, tempdb setup, high-cost-query inventory, blocking and wait trends, job health, and capacity indicators — delivered as prioritized findings with remediation recommendations.

Safe by construction

Beyond queries

Ad hoc reporting, data profiling, duplicate and null analysis, referential-integrity checks, record reconciliation, source-to-target comparison, trend and exception reporting, business-rule validation, and data-quality scoring — with findings explained in nontechnical language and exportable to JSON, CSV, text, or reports. Query history, saved queries, reusable prompt templates, team collaboration, and API access round out the platform.

Who it's for

SQL developersDBAsSoftware engineers Data analystsSupport engineersApplication teams Technical consultantsOperations teamsBusiness users with controlled access

Point it at a real problem.

Bring a slow query, an ugly incident, or a reporting backlog — we will show you what it does with it.

Start a conversation