burstable new limitations

Author: siddsawant

articles/mysql/flexible-server/concepts-service-tiers-storage.md

@@ -110,7 +110,12 @@ To get more details about the compute series available, refer to Azure VM docume
 Burstable compute tier is designed to provide a cost-effective solution for workloads that don't require continuous full CPU continuously. This tier is ideal for nonproduction workloads, such as development, staging, or testing environments.
 The unique feature of the burstable compute tier is its ability to “burst”, that is, to utilize more than its baseline CPU performance using up to 100% of the vCPU when the workload requires it. This is made possible by a CPU credit model, [which allows B-series instances to accumulate “CPU credits”](../../virtual-machines/b-series-cpu-credit-model/b-series-cpu-credit-model.md#b-series-cpu-credit-model) during periods of low CPU usage. These credits can then be spent during periods of high CPU usage, allowing the instance to burst above its base CPU performance.
 
-However, it’s important to note that once a burstable instance exhausts its CPU credits, it operates at its base CPU performance. For example, the base CPU performance of a Standard_B1s is 20% that is, 0.2 Vcore. If Burstable tier server is running a workload that requires more CPU performance than the base level, and it has exhausted its CPU credits, the server may experience performance limitations and eventually could affect various system operations for your server.
+However, it’s important to note that once a burstable instance exhausts its CPU credits, it operates at its base CPU performance. For example, the base CPU performance of a Standard_B1s is 20% that is, 0.2 Vcore. If Burstable tier server is running a workload that requires more CPU performance than the base level, and it has exhausted its CPU credits, the server may experience performance limitations and eventually could affect various system operations like Stop/Start/Restart for your server.
+
+>[!NOTE]
+>For servers in [Burstable (B-series) compute tier](../../virtual-machines/sizes-b-series-burstable.md), such as Standard_B1s/Standard_B1ms/Standard_B2s, their relatively smaller host memory size,  may lead to crashes (out of memory) under continouous workload, even if the [memory_percent](./concepts-monitoring.md#list-of-metrics) metric has not reached 100%. 
+
+Due to this throttling, the server may encounter **connectivity issues** and system operations might be affected. In such situations, the recommended course of action is to **pause the workload on the server** to accumulate credits according to the [B-series credit banking model](../../virtual-machines/b-series-cpu-credit-model/b-series-cpu-credit-model.md#b-series-cpu-credit-model), or to consider scaling the server to higher tiers such as **General Purpose** or **Business Critical** tiers.
 
 Therefore, while the Burstable compute tier offers significant cost and flexibility advantages for certain types of workloads, **it is not recommended for production workloads** that require consistent CPU performance. The Burstable tier doesn't support functionality of creating [Read Replicas](./concepts-read-replicas.md) and [High availability](./concepts-high-availability.md) feature. For such workloads and features, other compute tiers, such as the General Purpose or Business Critical are more appropriate.