An Azure relational database service.
@Rohit Kulkarni Thank you for reaching out.
You can use SHRINKDATABASE if you have a high number of Truncate, Delete table operations or ETL operations on this database
Otherwise, it is usually not required to manually shrink a database. Some best practices are here
Please be aware that after shrinking the database, indexes may become fragmented and lose their performance optimization effectiveness.
You should use an index maintenance solution like SQL Server Index and Statistics Maintenance to rebuild and reorganize indexes after a shrink operation.
Do let us know if you have any further questions.
----------
If an answer is helpful, please "Accept answer" or "Up-Vote" which might help other community members reading this thread.