Refresh Data
refresh triggers processing at model, table, or partition scope and can also provide a best-effort “is something refreshing right now?” status check.
Use it when:
- you changed partitions or schema and want to validate on fresh data,
- you need to confirm that a processing request was submitted,
- you want to run a calculate-only processing pass (when appropriate).
You typically won’t call the tool directly-tell the LLM what you want refreshed and why, and it will use refresh safely.
What to ask the LLM (quick prompts)
“Refresh the whole model (Full) and then re-run the validation queries.” “Refresh tableSales (DataOnly).”
“Refresh partition p2025_01 in table Sales (DataOnly).”
“Check refresh status only; don’t start a refresh. Include details.”
Scopes (what you can refresh)
You can refresh at:
- Model: processes all tables.
- Table: processes all partitions of a table.
- Partition: processes a specific partition in a table.
If you’re not sure what partitions exist:
“List partitions for tableSales and then refresh the right one.”
Refresh types (what “Full / DataOnly / Calculate” mean)
The tool supports three processing types:
- Full: standard processing (data + calculations as needed).
- DataOnly: process data without forcing a full calculation pass.
- Calculate: force calculation processing.
Important nuance (calculated tables):
- Some calculated tables/partitions don’t support
Full/DataOnlyprocessing in the engine. In those cases, the server may automatically fall back to Calculate to avoid errors.
If you care about exactly what will happen:
“Before refreshing, explain the chosen refresh type per table (especially for calculated tables).”Status-only checks (best-effort)
You can ask for status without triggering a refresh:
“Check status only for the model.” “Check status only for tableSales.”
“Check status only for partition p2025_01 in table Sales.”
What status means:
- The server inspects engine DMV state and returns a best-effort signal like “is a refresh-like command currently running?”.
- It does not guarantee a full “job history”, and it may miss work depending on host/engine behavior.
Prompt:
“Check refresh status only and include details (started time, elapsed, and command text).”Locked-down environments (mode behavior)
| Mode | Availability |
|---|---|
| Full mode | AvailableAvailable |
| Read-only mode | AvailableAvailable |
| Browse-only mode | Not availableNot available |
Notes: Status is best-effort; no cancel; may prompt on first model modification.
If refresh is blocked, ask:
“Explain whether refresh is blocked by mode or policy, and give me an alternative validation plan.”Common workflows
1) Refresh after partition work
“We changed partitions forSales. Refresh table Sales (DataOnly), then rerun the validation queries.”
2) Partition refresh (incremental patterns)
“Refresh partitionp2025_01 in table Sales (DataOnly), then check status with details.”
3) Calculate-only pass (targeted)
“Run a calculate refresh for the model and explain when this is the right choice vs Full/DataOnly.”4) “Don’t surprise me” safety pattern
“Before running refresh, summarize the exact scope and type you’ll execute, and wait for my confirmation.”Troubleshooting
You may be in browse-only mode, or your org policy restricts refresh. Ask for an allowed alternative: smaller validation queries, a manual refresh path, or an execution plan for a different environment.
Status is best-effort. Ask for status with details, or validate by running a query that checks known “freshness” indicators in your model (if you have them).
Refresh is treated as a model operation by the engine. If your client supports confirmations/elicitation, you may be prompted the first time in a session. If you don’t want refresh to run, decline and ask for a read-only validation plan.