Remove-LoaderDataset
Use the Remove-LoaderDataset cmdlet to manage the lifecycle of your automated data-loading logic. This command allows for the dynamic modification of the Startup Loader's dataset list, enabling administrators to retire obsolete or seasonal data-refresh routines without manual configuration file edits. This ensures your cache remains lean and its startup sequence remains deterministic as your application's data requirements evolve.
Remove-LoaderDataset -CacheName [-Port] [-Server] -Dataset [-Credentials]
Examples
- This command removes a dataset order on local server where the Startup Cache Loader and Refresher are enabled.
Remove-LoaderDataset -CacheName demoCache -Dataset "order"
- This command removes a dataset order from the cache named demoCache existing on the server 20.200.20.11, where the Startup Cache Loader and Refresher are enabled.
Remove-LoaderDataset -CacheName demoCache -Server 20.200.20.11 -Dataset "order"
- This command removes a dataset order on local server where the Startup Cache Loader and Refresher are enabled, using security credentials.
Remove-LoaderDataset -CacheName demoCache -Dataset "order" -Credentials(Get-Credential john_smith)
Properties
Note
The parameters with asterisk (*) on their names are the required parameters and the rest are optional.
| Parameters | Data Types | Description | Default Value |
|---|---|---|---|
-CacheName* |
<String> |
Specifies name of the cache registered on the server. The dataset will be removed from this specific cache. Note: The cache must already exist on the source server. |
- |
-Port |
<Integer> |
Specifies the port on which NCache Service is listening. | 8250 |
-Server |
<String> |
Specifies a server name where the NCache Service is running and a cache with the specified cache-name is registered. | IP of local machine |
-Dataset* |
<String> |
Specifies the name of the dataset that needs to be removed. | - |
-Credentials |
<pscredential> |
Specifies the user credentials required to authorize access for the specified operation. These credentials should belong to a user with the appropriate permissions at the node. | - |
