Check Index Usage
Review SQL Server index read and write activity, identify low-value indexes, and decide what deserves deeper analysis before any index is removed.
Javi Builds Data • AI • Cloud Engineering
Fast answers for real engineering problems.
Practical references for troubleshooting, implementation and production engineering across SQL Server, Python, Microsoft Fabric, PySpark, Git, APIs, Data Engineering, and AI Engineering for Data.
Not sure which technology page to open? Pick the situation you are in.
Search everything on the site with Ctrl + K; the box below filters this list only.
Review SQL Server index read and write activity, identify low-value indexes, and decide what deserves deeper analysis before any index is removed.
Measure SQL Server table row counts and storage usage, separate data from index space, and identify which tables are driving database growth.
Identify blocked sessions, blockers, lock waits, and the head blocker so you can troubleshoot SQL Server blocking without killing the wrong session.
Identify SQL Server queries consuming the most CPU now and historically, distinguish total CPU from CPU per execution, and choose the right next tuning step.
Identify SQL Server queries performing the most logical and physical reads, separate read-heavy workload from CPU-heavy workload, and choose the right next tuning step.
Identify long-running SQL Server requests and historical slow queries, separate elapsed time from CPU time, and determine whether the delay comes from waits, blocking, reads, or plan regression.
Use SQL Server missing-index DMVs as a triage signal, rank candidates by estimated impact, and validate each recommendation before creating an index.
Identify open transactions, find sessions holding them, measure transaction age, and connect long-running transactions to blocking, log growth, and application behavior.
Find recently executed stored procedures, compare execution counts and resource usage, and understand the limits of SQL Server procedure-cache statistics.
Quickly identify active SQL Server requests, what they are executing, how long they have been running, what resources they are consuming, and whether they are waiting or blocked.
Inspect a SQL Server session in detail, including request state, waits, transaction context, client metadata, SQL text, and execution-plan handles.
Use SQL Server Query Store to find regressions, compare plans, analyze runtime history, force or unforce plans safely, and understand when Query Store data can mislead you.
Group SQL Server activity by login, host, application, and database so you can identify which client or workload is generating connections, requests, CPU, reads, or blocking.
Use a repeatable SQL Server troubleshooting flow to separate blocking, CPU, I/O, waits, query regressions, and workload pressure before changing anything.
Use SQL Server wait statistics to identify where work is spending time, distinguish current waits from cumulative waits, and choose the next performance investigation.
Diagnose common pandas failures involving dtypes, missing values, joins, chained assignment, duplicate data, datetime errors, memory pressure, and unexpected row-count changes.
Filter pandas DataFrame rows safely and clearly using boolean masks, multiple conditions, membership tests, string/date filters, null checks, and query expressions.
Group pandas data by business keys, calculate reliable aggregations, preserve row-level context with transform, and avoid common mistakes with nulls, duplicates, and mixed aggregation logic.
Inspect, filter, fill, drop, and validate missing values in pandas without silently changing the meaning or dtype of production data.
Inspect a pandas DataFrame quickly and safely to understand its shape, columns, data types, nulls, duplicates, distributions, and suspicious values before transforming data.
Join pandas DataFrames safely by validating keys, cardinality, null behavior, duplicate expansion, and row-count changes before trusting the result.
Inspect and convert pandas data types safely, preserve nullability, detect failed conversions, and avoid silent schema changes in production data pipelines.
Read and write CSV, Parquet, and JSON with pandas while controlling schema, dates, nulls, compression, encoding, and production-safe file behavior.
Sort, rank, and deduplicate pandas data safely by defining deterministic order, business keys, tie behavior, and the exact row that should survive.
Parse, compare, filter, normalize, localize, convert, group, and validate dates and timestamps in pandas without introducing timezone or boundary errors.
Troubleshoot Microsoft Fabric pipeline failures by isolating the failed activity, separating transient from deterministic errors, validating parameters and identities, and using retries, logging, and controlled reruns safely.
Read and write Delta tables in Microsoft Fabric safely using append, overwrite, MERGE, partitioning, schema controls, concurrency-aware patterns, and table maintenance.
Design a practical Bronze, Silver, and Gold architecture in Microsoft Fabric with clear data contracts, replayability, incremental processing, quality gates, and serving responsibilities.
Troubleshoot and improve Microsoft Fabric notebook performance by separating Spark session startup, data scan, shuffle, skew, driver pressure, concurrency, and write-path bottlenecks.
Use Microsoft Fabric session tags to reuse compatible Spark sessions across notebook activities, reduce startup overhead, and avoid unnecessary session fragmentation.
The Kusto Query Language (KQL) a Microsoft Fabric data engineer uses most in Eventhouse and KQL querysets: filter, shape, sort, summarize, time windows with bin(), joins, nulls and dynamic fields, with a SQL-to-KQL mapping and seven practice exercises.
Choose between Microsoft Fabric Lakehouse and Warehouse by comparing development model, data types, SQL capabilities, transactions, ingestion patterns, and downstream analytics requirements.
The Microsoft Fabric workspace settings that change how a data engineering workspace behaves: Spark pools, environments and jobs, domain assignment, OneLake shortcut caching and diagnostics, and data workflow (Apache Airflow job) runtime pools, with what to verify for each.
Monitor Microsoft Fabric pipelines and notebooks using Monitoring hub, Workspace Monitoring, Spark monitoring, KQL, alerts, and capacity telemetry so failures and performance regressions become observable.
Aggregate PySpark DataFrames safely by defining output grain, handling null grouping keys, choosing correct aggregate functions, validating totals, and controlling shuffle-heavy groupBy workloads.
Join PySpark DataFrames safely by validating key cardinality, choosing the right join type and strategy, avoiding row multiplication, and handling skew, nulls, and ambiguous columns.
Troubleshoot and optimize PySpark workloads by separating scan, shuffle, skew, partitioning, caching, joins, driver pressure, and file-layout problems before changing cluster size.
Read and write Delta tables with PySpark using safe append, overwrite, merge, schema-evolution, partitioning, and maintenance patterns for production data pipelines.
Select, project, filter, and validate PySpark DataFrames efficiently while avoiding ambiguous columns, null-logic mistakes, unnecessary scans, and driver-side filtering.
Use PySpark window functions safely for ranking, latest-row selection, running totals, lag/lead analysis, and partitioned calculations without collapsing DataFrame grain.
Create, update, compare, merge, and clean up Git branches safely while preserving shared history and avoiding accidental divergence or destructive conflict resolution.
Use the Git commands engineers need most often for inspecting changes, creating commits, syncing branches, reviewing history, and recovering from common local mistakes.
Use Git stash safely to park unfinished work, switch context, inspect and restore stashed changes, handle untracked files, and recover when stash application conflicts.
Rebase Git branches safely to replay local commits onto a new base, resolve conflicts deliberately, clean up private history, and recover when a rebase goes wrong.
Resolve Git merge conflicts safely by identifying the operation in progress, understanding ours and theirs, reviewing the intended combined result, and completing or aborting the merge without losing work.
Undo Git changes safely by choosing the right command for unstaged edits, staged changes, local commits, or shared history without destroying work accidentally.
Choose and implement API authentication safely by understanding API keys, Basic auth, Bearer tokens, OAuth 2.0, JWTs, service identities, mTLS, token lifetimes, and common production failure modes.
Design and consume paginated APIs safely using offset, page-number, cursor, keyset, and continuation-token patterns with clear ordering, stable traversal, and production-safe client behavior.
Use cURL to test and troubleshoot HTTP APIs with practical patterns for methods, headers, authentication, JSON bodies, files, redirects, timeouts, retries, response inspection, and safe production diagnostics.
Interpret and use HTTP status codes correctly when building and troubleshooting APIs, with practical guidance for success, redirects, client errors, server errors, retries, and API design decisions.
Troubleshoot failing or slow API requests by isolating DNS, TLS, authentication, routing, rate limits, payloads, gateways, application errors, retries, and downstream dependencies.
Choose between batch and streaming data processing by comparing latency, correctness, operational complexity, cost, replay, state, and failure recovery for real production workloads.
Choose between CSV, JSON, Parquet, and Delta based on schema, analytics performance, mutability, interoperability, reliability, and production data-lake requirements.
Build practical data quality checks for schema, completeness, uniqueness, validity, referential integrity, freshness, reconciliation, and pipeline drift without relying on arbitrary universal thresholds.
Design safe incremental loads using watermarks, CDC, high-water marks, MERGE, idempotent writes, late-data handling, and replayable checkpoints without skipping or duplicating data.
Design Bronze, Silver, and Gold data layers with clear ownership, replayability, quality gates, incremental processing, and serving contracts without turning medallion architecture into rigid folder naming.
Choose and validate data partitioning strategies that improve pruning, parallelism, maintenance, and cost without creating skew, tiny files, or high-cardinality layouts.
A practical framework for choosing an AI model for data applications: when not to use an LLM, which dimensions matter, a decision tree, and how to evaluate candidates on quality, latency and cost per successful task.
Decide what to send to an LLM and in what order: a context priority model, token budgets per section, pruning, history summarization, retrieval limits, stale and conflicting context, and long-context trade-offs.
Estimate and control LLM workload cost with simple formulas for cost per request, per day and per month, plus token budgets, model tiering, caching, batch workloads and monitoring.
Reduce LLM token usage in data applications without losing the context or answer quality you need: measure first, trim prompts and history, limit retrieval, compact outputs, cache and route.
Reusable prompt patterns for data engineering tasks such as SQL generation, schema interpretation, column mapping, data-quality rules and incident analysis, with structured output, explicit assumptions and validation.