Sql Pro

**Quick judgment:** Sql Pro is a strong, specialized skill for SQL-heavy workloads—particularly valuable for performance tuning, complex query design, and cross-database work. It is best seen as a “virtual senior SQL developer” rather than a general-purpose data tool. **Key strengths and benefits** - Handles advanced SQL patterns: CTEs, window functions, recursive queries, OLAP-style analytics. - Explicit performance focus: encourages EXPLAIN/ANALYZE use, covering indexes, and early filtering. - Cross-engine awareness: targets PostgreSQL, MySQL, SQL Server, and Oracle with dialect guidance. - Good process discipline: analyze → design → optimize → verify → document, which helps maintainability. - Built-in guardrails: discourages SELECT *, cursors, ignoring execution plans, and poor NULL handling. **Risks and limitations** - **No direct database visibility:** All advice is based on described schemas and query plans; if the user’s description is incomplete or inaccurate, the recommendations can be suboptimal or wrong. - **Potential for unsafe operations:** It can suggest powerful DDL/DML (indexes, schema changes, ETL patterns); if users execute these without review or backups, they may experience data loss, lock contention, or downtime. - **Engine-specific edge cases:** Despite dialect guidance, subtle differences in query planners, isolation levels, or optimizer hints can lead to unexpected behavior if suggestions are copied blindly between platforms. - **Performance claims not guaranteed:** Sub-100ms targets are aspirational; actual performance depends heavily on data distribution, hardware, and concurrent workload. **Recommended scenarios** - You have specific slow queries and can provide `EXPLAIN`/`EXPLAIN ANALYZE` output and table definitions. - You are designing or refactoring complex reporting/analytics SQL with window functions and CTEs. - You need help choosing or refining indexes (including covering/compound indexes) for critical endpoints. - You are migrating SQL between PostgreSQL/MySQL/SQL Server/Oracle and want safe, idiomatic equivalents. - You are designing schemas or data warehousing structures (star schemas, SCDs, partitioning) and need performance-conscious guidance. Use Sql Pro when you can share concrete schemas, sample queries, and query plans, and when you are prepared to review and test all generated SQL in a non-production environment before rollout.