Although this might not seem to be relevant to high availability with MS SQL Server, it can, if neglected, lead to downtime because the database runs out of space. It is far better to anticipate this problem than to recover from it.
1. You install your database optimally for production.
You can prevent problems arising by optimal installation of your database, taking account of the disks available and anticipated future space requirements. For more information, see Disk Configuration.
2. You set the size for database files. This reduces the chance that your database will run out of space, which causes the database and the SAP system to stop processing.
3. You monitor the database closely during production, making sure that the data disk and the log does not fill up. For more information on checking the available disk space in the drives containing the SAP data and log files, see:
4. If the monitoring indicates that the database or log files are running out of space, you move them to a new disk in good time.