run-handsfree-indexing
Prepare, deploy, validate, rehearse, monitor, or clean up the SQLCon EU 2026 Caldova Hands-Free Indexing demo. Use for Azure SQL automatic indexing, Automatic Index Compaction, the Hyperscale dashboard workload, index bloat, compaction progress, or the demo's Azure deployment scripts.
- License 许可
- MIT
- 最近更新
- 2026-11-01
- Stars
- ★ 3
- Forks
- 0
01 前言 Front Matter
- name
- run-handsfree-indexing
- description
- Prepare, deploy, validate, rehearse, monitor, or clean up the SQLCon EU 2026 Caldova Hands-Free Indexing demo. Use for Azure SQL automatic indexing, Automatic Index Compaction, the Hyperscale dashboard workload, index bloat, compaction progress, or the demo's Azure deployment scripts.
- argument-hint
- Mode: prepare, deploy, preflight, rehearse, status, or cleanup
03 SKILL.md 正文
Run Hands-Free Indexing
Guide the user through the existing Azure SQL Database Hyperscale demo. Treat
the package README and
demo runbook as the
sources of truth. Run only the wrappers in deploy; do not reproduce their
Azure CLI or SQL logic manually.
Invariants
- Use the unchanged
demo.usp_PatientAccessDashboardprocedure. - The qualifying nonclustered index must be created by Azure SQL and report
auto_created = 1. - Never create a manual fallback index, force a plan, add a query hint, or drop and recreate the automatic index.
- Bloat and compaction eligibility must use the existing bounded insert/delete workloads. Never update surviving rows.
- Pair
DETAILEDphysical statistics with the latest real dashboard duration and logical reads. Never invent or interpolate measurements.
Safety Rules
- Confirm the Azure account, tenant, subscription, resource group, SQL region, App Service region, and vCore count before deployment.
- Explain that deployment creates billable Azure SQL Hyperscale, App Service,
networking, private endpoint, and DNS resources. Require explicit user
approval immediately before
01-deploy-infrastructure.ps1. - Require explicit approval before database initialization, bloat creation, enabling compaction, and cleanup.
99-remove.ps1deletes the entire configured resource group. Show the exact resource group and require confirmation before running it; do not suppress its PowerShell confirmation.- Do not request credentials in chat. Authentication must use Azure CLI, Microsoft Entra, and managed identity as implemented by the scripts.
- Do not print access tokens or broaden the exact-IP bootstrap firewall rule.
Select a Mode
prepare: validate tools, identity, configuration, and feature availability.deploy: run the four documented deployment steps with approval gates.preflight: verify an existing environment without changing it.rehearse: guide the measured indexing lifecycle one phase at a time.status: capture the current documented state once; do not poll continuously.cleanup: remove the dedicated resource group after explicit confirmation.
Prepare
- Read
deploy\00-config.ps1; do not run it directly. - Require PowerShell 7, Azure CLI, go-sqlcmd, and the .NET 10 SDK.
- Require
AZURE_SUBSCRIPTION_ID. Accept only the documented optionalCALDOVA_*environment overrides. - Use read-only account checks to confirm the active identity and that the
configured subscription matches
AZURE_SUBSCRIPTION_ID. - Confirm the selected SQL region supports the Automatic Index Compaction
preview. If this cannot be verified, stop and mark the gate
NOT VERIFIED. - Summarize the resolved resource names and locations without exposing tokens.
Deploy
From corenote\handsfreeindexing, run one step at a time and require success
before continuing:
-
After billable-resource approval:
.\deploy\01-deploy-infrastructure.ps1 -
After confirmation that recreating the isolated demo schema and loading two million rows is intended:
.\deploy\02-initialize-database.ps1 -
Publish the application:
.\deploy\03-publish-app.ps1 -
Verify the deployed environment:
.\deploy\04-verify.ps1
Require an online Hyperscale database, Entra-only authentication, an approved
private endpoint, a running Windows App Service, /healthz = ok, and
/readyz = ready.
Preflight
Run 04-verify.ps1 and report each documented gate. Confirm the presenter can
open the Operations Dashboard and Index Health views. Do not initialize data,
run workload, create bloat, or enable compaction during preflight.
Rehearse
Guide one phase at a time and wait for the user between phases:
- No Nonclustered Index: initialize only if a fresh environment is
explicitly intended; refresh the dashboard and confirm
Missing Index. - Automatic Tuning: run one 15-minute interval with
05-run-workload.ps1, then run06-show-index-recommendation.ps1and07-check-auto-index.ps1. If the index is not ready, stop and tell the user to repeat later. Never loop unattended. - Create Real Bloat: only after
auto_created = 1is proven and the user approves, run08-create-bloat.ps1. Refresh the dashboard, then run10-check-progress.ps1once. - Automatic Index Compaction: after approval, run
09-enable-compaction.ps1. On user request, refresh the dashboard and run10-check-progress.ps1once per observation. - Complete only when measured telemetry shows materially fewer pages, higher density, and recovered query performance. Preserve the runbook's final presentation message.
Automatic tuning and compaction are asynchronous. Do not claim completion from elapsed time alone and do not use sleep loops or continuous polling.
Status
Run 10-check-progress.ps1 once and summarize phase, index name,
auto_created, page count, density, logical reads, query duration, and AIC
state from the output. If no paired measurement exists, say so.
Cleanup
Show the resolved resource group, explain that every contained resource will be deleted, obtain explicit confirmation, and then run:
.\deploy\99-remove.ps1
Report that deletion was started; do not claim completion until Azure confirms the resource group no longer exists.
Completion Report
Report mode, subscription name, resource group, commands run, gates passed, current lifecycle phase, and remaining asynchronous or manual work. Do not include tokens or credentials.
04 同仓库更多 Skills
keynote-demo-app
Build or extend a SQLCon EU 2026 keynote demo application so it looks and behaves like the other keynote apps. Use when creating a new demo view (invoices, operations, orders), restyling an existing app to match, adding a deliberate database anti-pattern for a troubleshooting demo, or wiring an app to Azure SQL or Fabric SQL with managed identity. Triggers include "make this look like the keynote app", "build a demo view", "add the slow query demo", "match Caldova styling".
validate-post-migration-data
Validate data and schema after migrating SQL Server to Azure SQL Database, Azure SQL Managed Instance, or SQL Server on Azure VM. Use after migration, restore, BACPAC import, LRS completion, cutover validation, row-count comparison, or source-target reconciliation.
sql-server-to-sql-mi-lrs-migration
Migrate SQL Server databases to Azure SQL Managed Instance with Log Replay Service (LRS) using managed identity for Blob access. Use for SQL Server to SQL MI, LRS, log replay, continuous restore, or low-downtime backup-chain migrations.
sql-bacpac-to-azure-sql-db-migration
Migrate one or all user databases from SQL Server to Azure SQL Database with an offline BACPAC workflow. Use for BACPAC, SqlPackage export/import, bulk database migration, or offline Azure SQL Database migration requests.
sql-backup-restore-to-azure-sql-vm-migration
Migrate a SQL Server 2008 through SQL Server 2025 source to a SQL Server 2025 target wherever it runs, including SQL Server on Azure VM, by creating a local full backup, uploading it to Azure Blob Storage with AzCopy and the operator's Microsoft Entra identity, and restoring from URL with the target SQL Server managed identity. Sources newer than SQL Server 2025 are blocked because target restore compatibility has not been validated. Use for SQL-to-SQL, local-backup, AzCopy, managed-identity, Azure SQL VM, or SQL Server 2025 restore migrations.
run-migration-assessment
Route generic or unresolved SQL Server assessment, readiness, compatibility, cost, and SKU recommendation requests. Use for bare server names or whenever Azure versus local/on-premises is not explicit; ask which source applies, then delegate.