Final answer:
A dropped elastic pool database in Microsoft Azure is restored with the same configuration it had before and can be part of an elastic pool if restored directly into one, or added manually afterwards.
Step-by-step explanation:
When an elastic pool database is dropped and subsequently restored in Microsoft Azure, it is typically restored with the same configuration it had prior to being dropped, assuming the restored point is within the retained period. However, whether it returns as a part of an elastic pool depends on how the restore is performed. If you restore the database to an elastic pool directly, it becomes a part of that pool. Otherwise, if you restore the database as a single database and then want it to be part of an elastic pool, you'd have to manually add it to the pool post-restoration.
Procedure for Restoring to Elastic Pool
- Select the intended restore point for the database.
- Specify the target elastic pool you want the database to be part of.
- Confirm the restoration, and the database should be added to the pool upon completion.
It's important to note that restoring a database will incur a brief period of downtime as the data is rehydrated from backup resources.