SOLVED

Azure SQL Hyperscale Best Practices

Copper Contributor

I am hoping you can help answer this question. Previously whenever we upgraded or downgraded a SQL database, we always followed best practices. This included do the following three things:

  1. Rebuild all indexes
  2. Update Statistics
  3. Clear Procedure Cache

 

We have now moved to HyperScale and the databases will scale up and down as needed. Do we need to continue doing these best practices or is this taken care of in Azure automatically? Thank you.

1 Reply
best response confirmed by ParthKhemka (Copper Contributor)
Solution
Hi,

Even before HyperScale, using other service levels of Azure SQL, these 3 tasks are not needed at all when scaling up or down an Azure SQL Database.

Take a look on this video for a more in depth explanation about hyperscale: https://youtu.be/vH9XM9Ulc_g?list=PLNbt9tnNIlQ5i3hWhnwU3VqRxC-GPcol8&t=2481

Kind Regards,

Dennes
1 best response

Accepted Solutions
best response confirmed by ParthKhemka (Copper Contributor)
Solution
Hi,

Even before HyperScale, using other service levels of Azure SQL, these 3 tasks are not needed at all when scaling up or down an Azure SQL Database.

Take a look on this video for a more in depth explanation about hyperscale: https://youtu.be/vH9XM9Ulc_g?list=PLNbt9tnNIlQ5i3hWhnwU3VqRxC-GPcol8&t=2481

Kind Regards,

Dennes

View solution in original post