Re-organize and update article a little

Author: PiJoCoder

support/sql/database-engine/backup-restore/schedule-automate-backup-database.md

@@ -1,7 +1,7 @@
 ---
 title: Schedule and automate backups of databases
 description: This article describes how to use a Transact-SQL script and Windows Task Scheduler to automate backups of SQL Server Express databases on a scheduled basis.
-ms.date: 09/25/2020
+ms.date: 01/07/2025
 ms.custom: sap:Database Backup and Restore
 ms.topic: how-to
 ---
@@ -31,21 +31,21 @@ This article describes how to use a Transact-SQL script together with Task Sched
 > [!NOTE]
 > This applies to only SQL Server express editions and not to SQL Server Express LocalDB.
 
-## More information
+## How to create a scheduled backup in SQL Express
 
 You have to follow these four steps to back up your SQL Server databases by using Windows Task Scheduler:
 
-**Step A**: Create stored procedure to Back up your databases.
+### Step 1: Create stored procedure to Back up your databases
 
 Connect to your SQL express instance and create sp_BackupDatabases stored procedure in your master database using the script at the following location:
 
 [SQL_Express_Backups](https://raw.githubusercontent.com/microsoft/mssql-support/master/sample-scripts/backup_restore/SQL_Express_Backups.sql)
 
-**Step B**:  Download SQLCMD tool (if applicable).
+### Step 2:  Download the SQLCMD client utility
 
 The `sqlcmd` utility lets you enter Transact-SQL statements, system procedures, and script files. In SQL Server 2014 and lower versions, the utility is shipped as part of the product. Starting with SQL Server 2016, `sqlcmd` utility is offered as a separate download. For more information, review [sqlcmd Utility](/sql/tools/sqlcmd-utility).
 
-**Step C**: Create batch file using text editor.
+### Step 3: Create a batch file using a text editor
 
 In a text editor, create a batch file that is named *Sqlbackup.bat*, and then copy the text from one of the following examples into that file, depending on your scenario:
 
@@ -56,80 +56,75 @@ In a text editor, create a batch file that is named *Sqlbackup.bat*, and then co
 > [!NOTE]
 > The folder for the `SQLCMD` executable is generally in the Path variables for the server after SQL Server is installed or after you install it as stand-alone tool. But if the Path variable does not list this folder, you can either add its location to the Path variable or specify the complete path to the utility.
 
-**Example 1:** Full backups of all databases in the local named instance of SQLEXPRESS by using Windows Authentication.
+#### Example 1: Full backups of all databases in the local named instance of SQLEXPRESS by using Windows Authentication.
 
-```sql
+```console
  // Sqlbackup.bat
  sqlcmd -S .\SQLEXPRESS -E -Q "EXEC sp_BackupDatabases @backupLocation='D:\SQLBackups\', @backupType='F'"
 ```
 
-**Example 2:** Differential backups of all databases in the local named instance of SQLEXPRESS by using a SQLLogin and its password.
+#### Example 2: Differential backups of all databases in the local named instance of SQLEXPRESS by using a SQLLogin and its password.
 
-```sql
+```console
  // Sqlbackup.bat
 sqlcmd -U <YourSQLLogin> -P <StrongPassword> -S .\SQLEXPRESS -Q "EXEC sp_BackupDatabases  @backupLocation ='D:\SQLBackups', @BackupType='D'"
 ```
 
 > [!NOTE]
 > The SQLLogin should have at least the Backup Operator role in SQL Server.
 
-**Example 3:** Log backups of all databases in local named instance of SQLEXPRESS by using Windows Authentication
+#### Example 3: Log backups of all databases in local named instance of SQLEXPRESS by using Windows Authentication
 
-```sql
+```console
  // Sqlbackup.bat
  sqlcmd -S .\SQLEXPRESS -E -Q "EXEC sp_BackupDatabases @backupLocation='D:\SQLBackups\',@backupType='L'"
 ```
 
-**Example 4:** Full backups of the database USERDB in the local named instance of SQLEXPRESS by using Windows Authentication
+#### Example 4: Full backups of the database USERDB in the local named instance of SQLEXPRESS by using Windows Authentication
 
-```sql
+```console
  // Sqlbackup.bat
  sqlcmd -S .\SQLEXPRESS -E -Q "EXEC sp_BackupDatabases @backupLocation='D:\SQLBackups\', @databaseName='USERDB', @backupType='F'"
 ```
 
 Similarly, you can make a differential Backup of USERDB by pasting in 'D' for the **@backupType** parameter and a log Backup of USERDB by pasting in 'L' for the **@backupType** parameter.
 
-**Step D:** Schedule a job by using Windows Task Scheduler to execute the batch file that you created in step B. To do this, follow these steps:
+### Step 4:  Schedule a job by using Windows Task Scheduler to execute the batch file that you created in step 2
+
+Follow these steps:
 
 1. On the computer that is running SQL Server Express, click **Start**, then in the text box type *task Scheduler*.
 
      :::image type="content" source="media/schedule-automate-backup-database/task-scheduler.png" alt-text="Screenshot of the Task Scheduler Desktop app option in the search bar of Start menu." border="false":::
 1. Under **Best match**, click **Task Scheduler** to launch it.
-
 1. In Task Scheduler, right-click on **Task Schedule Library** and click on **Create Basic task…**.
-
 1. Enter the name for the new task (for example: SQLBackup) and click **Next**. 
-
 1. Select **Daily** for the Task Trigger and click **Next**. 
-
 1. Set the recurrence to one day and click **Next**. 
-
 1. Select **Start a program** as the action and click **Next**. 
-
 1. Click **Browse**, click the batch file that you created in Step C, and then click **Open**.  
-
 1. Check the box Open the Properties dialog for this task when I click **Finish**. 
-
 1. In the General tab,
-
-    1. Review the Security options and ensure the following for the user account running the task (listed under  When running the task, user the following user account:)
+   - Review the Security options and ensure the following for the user account running the task (listed under  When running the task, user the following user account:)
 
         The account should have at least Read  and Execute permissions to launch sqlcmd utility. Additionally,
 
         - If using Windows authentication in the batch file, ensure the owner of the task permissions to do SQL Backups.
 
         - If using SQL authentication in the batch file, the SQL user should have the necessary permissions to do SQL Backups.
 
-    1. Adjust other settings according to your requirements.
+    - Adjust other settings according to your requirements.
 
 > [!TIP]
 > As a test, run the batch file from Step C from a command prompt that is started with the same user account that owns the task.
 
-Be aware of the following when you use the procedure that is documented in this article:
+### Requirements
+
+Be aware of the following requirements when you use the procedure that is documented in this article:
 
 - The Task Scheduler service must be running at the time that the job is scheduled to run. We recommend that you set the startup type for this service as **Automatic**. This makes sure that the service will be running even on a restart.
 
-- There should be lots of space on the drive to which the backups are being written. We recommend that you clean the old files in the Backup folder regularly to make sure that you do not run out of disk space. The script does not contain the logic to clean up old files.
+- You must create sufficient amount of space on the drive where the backups are written. We recommend that you clean old files in the Backup folder regularly to make sure that you do not run out of disk space. The script doesn't contain the logic to clean up old files.
 
 ## Additional references