For more information about these commands, see Storage emulator command-line tool reference. Or, you can use the following command, which reinitializes the database to the default LocalDB instance. You can also use the following command, which directs the emulator to use the default SQL Server instance. Open the Storage Emulator console window as described in the Start and initialize the storage emulator section. You can use the storage emulator command-line tool to initialize the storage emulator to point to a SQL database instance other than the default LocalDB instance. You can use the Microsoft Azure Storage Explorer to work with local storage emulator resources. The first time you run the storage emulator, the local storage environment is initialized for you. To bring up the Storage Emulator console window again, follow the preceding steps as if starting the storage emulator. When you close the storage emulator Command Prompt window, the storage emulator will continue to run. The Azure storage emulator may not start correctly if another storage emulator, such as Azurite, is running on the system. You can also clear data, get status, and initialize the emulator from the command prompt.įor more information, see the Storage emulator command-line tool reference section later in this article. You can use this console window to start and stop the storage emulator. When the storage emulator starts, a Command Prompt window will appear. Some differences in functionality exist between the storage emulator and Azure storage services.įor more information about these differences, see the Differences between the storage emulator and Azure Storage section later in this article. See the Start and initialize the storage emulator section later in this article to learn more. However, any version of OData supported by the storage service may be used to send requests to the emulator. Replacing the OData DLLs used by the storage emulator with other versions is unsupported, and may cause unexpected behavior. The storage emulator depends on specific versions of the OData libraries. If you need to persist your data for the long term, we recommended that you store that data in an Azure storage account, rather than in the storage emulator.
![run azure storage emulator from command line run azure storage emulator from command line](https://devnet.kentico.com/getattachment/6bf05152-fdb0-4338-8a28-a157e2f24092/AzureDB1.png)
Data created in one version of the storage emulator is not guaranteed to be accessible when using a different version. If you need a storage emulator for Linux, one option is the community maintained, open-source storage emulator Azurite. The storage emulator currently runs only on Windows.
#Run azure storage emulator from command line install#
To install the storage emulator, you must have administrative privileges on your computer. You can also install the storage emulator by using the standalone installer direct download. When you're satisfied with how your application is working in the emulator, switch to using an Azure storage account in the cloud. You can test your application against the storage services locally without creating an Azure subscription or incurring any costs.
![run azure storage emulator from command line run azure storage emulator from command line](https://mountainss.files.wordpress.com/2018/04/azcopy.png)
![run azure storage emulator from command line run azure storage emulator from command line](https://www.codeproject.com/KB/azure/1228709/WinAzureEmulatorExeDir.png)
The Microsoft Azure storage emulator is a tool that emulates the Azure Blob, Queue, and Table services for local development purposes.