ℹ️ Internal article. This action is an internal CRS operations job and is not intended for customer use. Contact support if the functionality is of interest to you.
Internal CRS operations job that crawls subscription, user and feature usage across all tenants and builds the license-billing star schema in the internal Azure SQL warehouse.
How to use the action
The action is an internal operations job that runs on a schedule at CRS. It requires administrator rights and direct database access and is not part of a normal customer setup.
Key parameters
Parameter | Explanation |
AzureSqlConnectionString | Connection string to the internal Azure SQL data warehouse that receives the results. |
DropAndRecreate | When enabled, drops and recreates the staging, final and snapshot tables before the run; use after a schema change. |
Platforms | Comma-separated list of platform database segments to iterate (default Prod02,Prod03,Prod05,Prod06). |
ReferenceDomain | The domain name of the CRS reference tenant whose schema is resolved at runtime. |
ReferencePlatform | The platform that holds the CRS reference tenant with the price list and subscription invoices (default Prod05). |
SaperaConnectionString | Connection string to the source SQL Server that hosts the production tenant databases. |
SkipCheckFor | Comma-separated platform=tenant pairs to exclude from the crawl. |
WriteMonthlySnapshot | When enabled, also archives the current facts into a monthly snapshot for trend analysis. |
See also the overview SyncTool – actions.
Want to know more?
Read more in these related articles:
Standard parameters for all actions
The general parameters available on most SyncTool actions: step control, error handling, timeout, etc.