With a click of a button, CosmosDB enables users to scale throughput and storage across any levels. Users can elastically scale and take advantage of fast, single-digit-millisecond data access.
Easily migrate your application, keep your application portable and continue to remain cloud vendor-agnostic and elastically scale the provisioned throughput and storage for your databases
Sprinkle supports a wide range of data sources. On clicking the “+sign”, a list of data sources pops up. In this case, Cosmos DB is selected. A new Cosmos DB is named and created.
After naming the data source, the configure tab would require the user to provide the “AccountEndPoint” and “Master Key” of Cosmos DB. The credentials can be tested if they are valid or not by testing the connection before updating.
Also users can select Yes or No to Optimize Incremental Ingestion. If optimize is Yes, all the datasets will undergo full ingestion on every Sunday. If optimize is No, data will be ingesting incrementally and it never goes under complete ingestion.
In Datasets, the user is required to specify a table name, Database Id, Collection Id and the way the user wants to ingest the data, either completely or incrementally.
On Selecting Incremental, the user must provide the Unique Key, this wouldn’t be the case when it comes to complete ingestion. The schema can also be set between automatic or manual. If it’s a manual schema, then the warehouse schema should also be specified. Sprinkle specializes in automatic schema features i.e. creating tables with automatic warehouse schema.
Tables can be ingested in four ways.
- Incremental loading with Start Date
- Incremental loading with No of days
- Complete loading with Start Date
- Complete loading with No of days
Incremental loading with Start Date
In this ingestion, during the first run complete data is pulled from the given Start Date and pulls data incrementally during weekdays. On every Sunday morning it goes under complete loading and pulls data from the Start Date, according to optimization choice.
Incremental loading with No of days
In this ingestion, during the first run data is pulled according to the number of days and pulls data incrementally during Weekdays. On every Sunday morning it goes under complete loading and pulls data from the number of days given, according to optimization choice. It won’t pull old data like in Start Date as ingestion is running based on the number of days.
Complete loading with Start Date
In this ingestion, it always loads data according to the Start date given.
Complete loading with No of days
In this ingestion, it always loads data according to the No of days given.
In the Ingestion Jobs tab, the concurrency (number of tables that can run in parallel, a maximum of 7) can be set preferentially before running the job. The status of the job will be updated in the tab below once it’s complete. The jobs can also be set to run automatically by enabling autorun. By default, the frequency is set to every night. Frequency can be changed by clicking on More --> Autorun-->Change Frequency.