--- title: "How to Create a Handy SQL Server Backup Database Script" description: "Learn how to backup your databases regularly, whether a full or differential backup, by creating handy SQL server database backup scripts in this tutorial!" canonical: "https://adamtheautomator.com/sql-server-backup-database-script/" --- # How to Create a Handy SQL Server Backup Database Script > Learn how to backup your databases regularly, whether a full or differential backup, by creating handy SQL server database backup scripts in this tutorial! Source: https://adamtheautomator.com/sql-server-backup-database-script/ --- ATA Learning Tap to hide [ ATA Learning ](/) * [Home](/) * [Tutorials](/tutorials/) * [Instructors](/author/) * [Advertising](/advertising/) * [Recommended Resources](/resources/) * [About Adam](/about-adam/) Search for: * [](https://twitter.com/adbertram) * [](https://github.com/Adam-the-Automator) * [](https://www.linkedin.com/company/adam-the-automator-llc) * [](/feed/) ![How to Create a Handy SQL Server Backup Database Script](https://adamtheautomator.com/wp-content/uploads/2022/03/How-to-Create-a-Handy-SQL-Server-Backup-Database-Script.jpg) # How to Create a Handy SQL Server Backup Database Script [![](https://secure.gravatar.com/avatar/26d98f5933e33a53463dd6b5bd002cbae84eb2e0b5c1f47aa8b452597c3f0f74?s=192&d=mm&r=g)Helen Mary Barrameda](https://adamtheautomator.com/author/helenmary-barrameda/)29 March 202211 min. read Categories: [Software Development](/category/software-development/) Tags:[SQL](/tag/sql/) Table of Contents * [Prerequisites](#prerequisites) * [Setting up your Backup Project Folder](#setting-up-your-backup-project-folder) * [Backing up a Database Following a Naming Convention](#backing-up-a-database-following-a-naming-convention) * [Performing Differential SQL Backup](#performing-differential-sql-backup) * [Backing up a Database in File-Level](#backing-up-a-database-in-file-level) * [Backing up Database in Multiple Folders](#backing-up-database-in-multiple-folders) * [Tracking the Backup Status with a Progress Bar](#tracking-the-backup-status-with-a-progress-bar) * [Adding a Backup Description](#adding-a-backup-description) * [Backing Up Multiple Databases in One Script](#backing-up-multiple-databases-in-one-script) * [Backing up Databases with Microsoft SSMS](#backing-up-databases-with-microsoft-ssms) * [Backing up a Database with a Reusable SSMS Generated Script](#backing-up-a-database-with-a-reusable-ssms-generated-script) * [Conclusion](#conclusion) If you’re administering a database, it’s only natural you’d be responsible for nurturing and caring for it. And what better care than backing up your databases regularly, so your data is safe? An SQL server backup database script is one of the best options. Backing up regularly gets even trickier when you manage multiple projects with lots of databases. Don’t let that worry you, though. In this tutorial, you’ll learn methods to backup your databases regularly by invoking SQL scripts. Read on and start backing up your databases! ## Prerequisites This tutorial will be a hands-on demonstration. To follow along, be sure you have the following: * An SQL Server (The [Developer Edition](https://www.microsoft.com/en-us/sql-server/sql-server-downloads) will suffice) – This tutorial uses an SQL Server instance named (SQLEXPRESS). Related:[Understanding SQL Server Data Types (And When to Use Them)](https://adamtheautomator.com/sql-server-data-types/) * An SQL Database to backup – This tutorial uses _AdventureWorksLT2019.bak_ from [AdventureWorks sample databases](https://docs.microsoft.com/en-us/sql/samples/adventureworks-install-configure?view=sql-server-ver16&tabs=ssms). * [SQL Server Management Studio (SSMS)](https://docs.microsoft.com/en-us/sql/ssms/download-sql-server-management-studio-ssms?view=sql-server-ver15) installed – This tutorial uses Microsoft SQL manager version 18. * [PowerShell](https://docs.microsoft.com/en-us/powershell/scripting/install/installing-powershell?view=powershell-7.2) installed on your device. This tutorial uses Windows PowerShell 5.1, but later versions will also work. * An [SQL administrative account](https://ph.godaddy.com/help/create-an-admin-user-for-microsoft-sql-server-19032). * A Windows 10 machine – This tutorial uses OS Build 19043.1288. ## Setting up your Backup Project Folder In this tutorial, the first method you’ll try is creating a [Transact-SQL (T-SQL)](https://docs.microsoft.com/en-us/sql/t-sql/language-reference?view=sql-server-ver15) script. T-SQL is a Microsoft-specific extension to the SQL language. [`sqlcmd`](https://docs.microsoft.com/en-us/sql/tools/sqlcmd-utility?view=sql-server-ver16) is a command-line utility tool that allows you to run SQL script files. And these script files perform tasks like backing up your databases. But before backing up your database, you’ll first have to verify if sqlcmd works and create a backup folder. 1\. Open [PowerShell as administrator](https://adamtheautomator.com/powershell-run-as-administrator/), and run the below command to verify if `sqlcmd` works on your PowerShell session. ```powershell sqlcmd -? ``` Below, you can see the sqlcmd command works, but the output may vary depending on the installed version. ![Verifying if the sqlcmd Command Works](https://adamtheautomator.com/wp-content/uploads/2022/03/image-452.png) Verifying if the sqlcmd Command Works 2\. [Restore your database to Microsoft SSMS](https://docs.microsoft.com/en-us/sql/relational-databases/backup-restore/quickstart-backup-restore-database?view=sql-server-ver15#restore-a-backup), in this case, _AdventureWorksLT2019.bak._ 3\. Lastly, create a folder to hold all your backups. For this tutorial, the folder is named _C:\\ata\_db._ The chosen path will be shown in the commands throughout this tutorial as _C:\\ata\_db\\name\_of\_your\_file._ ## Backing up a Database Following a Naming Convention Now that you have settled on a backup folder, it’s time to build the script. Typically, you’d want to identify a backup file at first glance. So, why not follow a naming convention for your backup files? For this tutorial, you can adopt the _YYYYMMDD\_HHMM\_DatabaseName.bak_ convention. The suggested convention stores the hour and minutes following the 24-hour layout (e.g., 2300 for 11 pm). > _You are free to follow a different convention, just be aware that you will need to change the commands in the scripts accordingly._ 1\. Open your favorite text editor, copy/paste the T-SQL content below, and save the file with your preferred name. But for this tutorial, the file is named _backup1.sql_ saved in the _C:\\ata\_db_ folder. The code below will consider a database named AdventureWorksLT2019 and store a backup created on November 16, 2021, at 11: 37 PM. Following the naming convention, the backup file will be named _20211116\_2337\_AdventureWorksLT2019.bak._ ```sql USE AdventureWorksLT2019; GO BACKUP DATABASE AdventureWorksLT2019 TO DISK = 'C:\ata_db\20211116_2337_DatabaseName.bak' GO ``` 2\. Now, run the following command to invoke _backup1.sql_ on your SQL server (`-S localhost\SQLEXPRESS`). Be sure to replace `SQLEXPRESS` with your SQL server’s instance name. ```powershell sqlcmd -S localhost\SQLEXPRESS -i C:\ata_db\backup1.sql ``` > _The command will work even if you have a remote database, such as an Azure-powered SQL database._ Related:[How to Create an Azure SQL Database](https://adamtheautomator.com/create-azure-sql-database/) As you see below, the backup was successful. ![Performing a Backup with Transact-SQL and sqlcmd](https://adamtheautomator.com/wp-content/uploads/2022/03/image-453.png) Performing a Backup with Transact-SQL and sqlcmd 3\. Lastly, open File Explorer, browse the backup folder you specified (_C:\\ata\_db_), and look for the backup file to confirm the backup file creation. ![Checking the Backup File was Created](https://adamtheautomator.com/wp-content/uploads/2022/03/image-454.png) Checking the Backup File was Created ## Performing Differential SQL Backup If you’re following along, you already performed your first full backup. But you’re not restricted to full backups! With the power of T-SQL, you can also perform a differential backup, which only stores the changes that happened since the previous full backup. 1\. Create a new file named _backup2.sql_ and populate the file with the code below. The code below will backup the AdventureWorksLT2019 database with the name 20220206\_1705\_AdventureWorksLT2019.bak_._ ```sql USE AdventureWorksLT2019; GO BACKUP DATABASE AdventureWorksLT2019 TO DISK = 'C:\ata_db\20220206_1705_AdventureWorksLT2019.bak' WITH DIFFERENTIAL GO ``` 2\. Now, run the command below to invoke the script (`backup2.sql`). You can change the absolute path specified into a relative path of your choice. ```powershell sqlcmd -S localhost\SQLEXPRESS -i C:\ata_db\backup2.sql ``` A successful differential backup will look like the one below. ![Using a Differential Backup Script for a Database](https://adamtheautomator.com/wp-content/uploads/2022/03/image-455.png) Using a Differential Backup Script for a Database 3\. Finally, check the _C:\\ata\_db_ folder and verify if the backup file you created in step two exists, as shown below. ![Checking the Differential Backup File](https://adamtheautomator.com/wp-content/uploads/2022/03/image-456.png) Checking the Differential Backup File ## Backing up a Database in File-Level SQL Server databases can have multiple files, and sometimes you can just cherry-pick or select the critical parts you want to back up. And you can use this file-level backup option for such purposes. 1\. Open your Microsoft SSMS, right-click on the **AdventureWorksLT2019** database and choose **Properties** to show the databases’ properties. To demonstrate how to back up a database in File Level, add a test file with the following: * Select the **Files** menu on the left panel, and click on the **Add** button at the bottom of the **Database Properties** window to create a ROWS data filegroup. * You can set a distinct **Logical Name**, **Filegroup**, and **File Name** for the new ROWS data filegroup. But for learning purposes, all three properties are set as **Test** in this tutorial, as shown below. Below, you can see the database files (log and data files). The data for AdventureWorksLT2019 is stored on two files. ![Showing files and filegroups of a database in SQL Server Management](https://adamtheautomator.com/wp-content/uploads/2022/03/image-457.png) Showing files and filegroups of a database in SQL Server Management 2\. Create a new script file, paste the contents below to the file, and save it as _C:\\ata\_db\\backup3.sql_. The code below backs up only the Test file as TestBackup\_TestBackup.FIL in the C:\\ata\_db folder. ```sql BACKUP DATABASE AdventureWorksLT2019 FILE = 'Test' TO DISK = 'C:\ata_db\TestBackup_TestBackup.FIL' GO ``` 3\. Now, run the command below to invoke the script (`backup3.sql`). ```powershell sqlcmd -S localhost\SQLEXPRESS -i C:\ata_db\backup3.sql ``` Once again, a successful backup will look like the one below. ![Backing up a Database Partially by Specifying the File ](https://adamtheautomator.com/wp-content/uploads/2022/03/image-458.png) Backing up a Database Partially by Specifying the File 4\. Lastly, navigate to _C:\\ata\_db_ in File Explorer to verify the backup file (_**TestBackup\_TestBackup.FIL**_) is present. ![Checking the Results of a File-Level Backup](https://adamtheautomator.com/wp-content/uploads/2022/03/image-459.png) Checking the Results of a File-Level Backup ## Backing up Database in Multiple Folders You’ve seen how to backup database in a single folder, but what if you need to backup your database in multiple folders? Backing up your database in multiple folders gives you high data availability. 1\. Create a folder called _C:\\secondfolder,_ where you’ll store a second backed up database later. 2\. Next, create a new script file (_backup4.sql_), and populate the file with the code below. The below code backs up the same database (AdventureWorksLT2019 ) to two different locations with different names. ```sql BACKUP DATABASE AdventureWorksLT2019 TO DISK = 'C:\ata_db\AW_first_backup.bak', DISK = 'C:\secondfolder\AW_second_backup.bak' GO ``` 3\. Finally, run the following command to invoke the SQL script (`backup4.sql`). ```powershell sqlcmd -S localhost\SQLEXPRESS -i C:\ata_db\backup4.sql ``` ![Creating two backup files in different folders for the same database](https://adamtheautomator.com/wp-content/uploads/2022/03/image-460.png) Creating two backup files in different folders for the same database The script generates two _.bak_ files on separate folders, as shown below. ![Showing the first backup on the original C:\\ata\_db folder](https://adamtheautomator.com/wp-content/uploads/2022/03/image-461.png) Showing the first backup on the original _C:\\ata\_db_ folder ![Showing file content in the C:\\secondfolder specified on backup4.sql Script](https://adamtheautomator.com/wp-content/uploads/2022/03/image-462.png) Showing file content in the _C:\\secondfolder_ specified on _backup4.sql_ Script ## Tracking the Backup Status with a Progress Bar Some database backups are lengthy, and it’s hard to decipher progress with a blinking cursor, so adding a progress bar helps. Create another script file named _backup5.sql_, and copy/paste the content below to the _backup5.sql_ file, which adds a progress bar. ```sql BACKUP DATABASE AdventureWorksLT2019 TO DISK = 'C:\\ata_db\\stats_backup.bak' WITH STATS GO ``` Now, run the `sqlcmd` command similar to previous steps to invoke the _`backup5.sql`_ script ```powershell sqlcmd -S localhost\\SQLEXPRESS -i C:\\ata_db\\backup5.sql ``` Once you invoke the script, you’ll see the progress of backing up the file as it happens, as shown below. ![Backing up AdventureWorksLT2019 database with stats progress option enabled](https://adamtheautomator.com/wp-content/uploads/2022/03/image-463.png) Backing up AdventureWorksLT2019 database with stats progress option enabled > _By default, the `WITH STATS` flag shows tracks in 10% steps. But perhaps you prefer to update the bar at every 1% for example, change the flag to `WITH STATS = 1`_ The file _stats\_backup.bak_ will now be present in your _C:\\ata\_db_ folder. ![Showing backup SQL script output that had progress stats in PowerShell. ](https://adamtheautomator.com/wp-content/uploads/2022/03/image-464.png) Showing backup SQL script output that had progress stats in PowerShell. ## Adding a Backup Description When managing many databases, it’s easy to get lost in a plethora of files. Adding a description for your backups allows you to backtrack and refer to the backup description in the future. Create a new script named _backup6.sql_ and populate the following contents. The code below backs up the `AdventureWorksLT2019` as `with_desc_backup.bak` with a description (`Full backup for AdventureWorks`). > _Your description for the backup can only have up to 255 characters._ ```sql BACKUP DATABASE AdventureWorksLT2019 TO DISK = 'C:\\ata_db\\with_desc_backup.bak' WITH DESCRIPTION = 'Full backup for AdventureWorksLT2019' GO ``` Now execute the following to invoke the _backup6.sql_ script. ```powershell sqlcmd -S localhost\\SQLEXPRESS -i C:\\ata_db\\backup6.sql ``` Once you invoke the script, you will see an output similar to the previous examples. ![Invoking the backup6.sql script to run a backup task](https://adamtheautomator.com/wp-content/uploads/2022/03/image-465.png) Invoking the _backup6.sql_ script to run a backup task ## Backing Up Multiple Databases in One Script By now, you’ve already learned different options to back up a single database. But your machine may have multiple databases. So instead, use an extended script to back up all your databases at the same time. 1\. Create a new script named _backup\_combo.sql_, and populate the code below to the _backup\_combo.sql_ file. > _The code is quite long, so you’ll add individual parts of the code to the script file in the sequence. You’ll see the entire code just before you invoke the script._ The code below declares four variables initially to represent the database name, path, name of the file for each database backup (the one with a _.bak_ extension), and date of the file backup. ```sql DECLARE @dbname VARCHAR(50) -- database name DECLARE @file_path VARCHAR(256) -- path DECLARE @file_name VARCHAR(256) -- DECLARE @file_date VARCHAR(20) -- used for filename SET @file_path = 'C:\ata_db\' ``` 2\. Next, add the code below to the _backup\_combo.sql_ file, where the `file_date` variable later stores the actual date and timestamp when the backup script was invoked. The [GETDATE() command](https://docs.microsoft.com/en-us/sql/t-sql/functions/getdate-transact-sql?view=sql-server-ver15) is in date format, so it’s converted into VARCHAR type first. That way, the date can be later concatenated in the file name of the database. Note that the following code captures all databases. So, you exclude other built-in system databases named master, model, msdb, and tempdb with the WHERE flag. ```sql SELECT @file_date = CONVERT(VARCHAR(20),GETDATE(),112) + '_' + REPLACE(CONVERT(VARCHAR(20),GETDATE(),108),':','') DECLARE db_cursor CURSOR READ_ONLY FOR SELECT name FROM master.sys.databases WHERE name NOT IN ('master','model','msdb','tempdb') -- these are system databases OPEN db_cursors FETCH NEXT FROM db_cursor INTO @dbname ``` 3\. Add the last part of the code to the _backup\_combo.sql_ file. The WHILE loop captures each database name fetched by the db\_cursor. The loop will keep fetching each database in the machine (FETCH\_NEXT statement) until it captures all the existing databases. ```sql WHILE @@FETCH_STATUS = 0 BEGIN SET @file_name = @file_path + @dbname + '_' + @file_date + '.BAK' BACKUP DATABASE @dbname TO DISK = @file_name FETCH NEXT FROM db_cursor INTO @dbname END CLOSE db_cursor DEALLOCATE db_cursor ``` As previously mentioned, you can see below the entire code for the _backup\_combo.sql_ file. The _backup\_combo.sql_ script file is like the other previous scripts. But this script file even automates the naming of each database in the machine by using date and time variables. ```sql DECLARE @dbname VARCHAR(50) -- database name DECLARE @file_path VARCHAR(256) -- path DECLARE @file_name VARCHAR(256) -- DECLARE @file_date VARCHAR(20) -- used for filename SET @file_path = 'C:\ata_db\' SELECT @file_date = CONVERT(VARCHAR(20),GETDATE(),112) + '_' + REPLACE(CONVERT(VARCHAR(20),GETDATE(),108),':','') DECLARE db_cursor CURSOR READ_ONLY FOR SELECT name FROM master.sys.databases WHERE name NOT IN ('master','model','msdb','tempdb') -- these are system databases OPEN db_cursor FETCH NEXT FROM db_cursor INTO @dbname WHILE @@FETCH_STATUS = 0 BEGIN SET @file_name = @file_path + @dbname + '_' + @file_date + '.BAK' BACKUP DATABASE @dbname TO DISK = @file_name FETCH NEXT FROM db_cursor INTO @dbname END CLOSE db_cursor DEALLOCATE db_cursor ``` 4\. Now, run the command below to invoke the entire script (_backup\_combo.sql_). ```powershell sqlcmd -S localhost\SQLEXPRESS -i C:\ata_db\backup_combo.sql ``` You’ll know the backup is successful when you see multiple processed statements for all the databases in your machine just like the one below. ![Backing up Multiple Databases using One Script](https://adamtheautomator.com/wp-content/uploads/2022/03/image-466.png) Backing up Multiple Databases using One Script Similarly, you’ll see the generated _.bak_ files on your specified folder accordingly. > _Note that your machine may contain different databases, so the file names and the contents will not be identical to the screenshot below._ ![Showing files from a combo backup script for all databases in a single instance. ](https://adamtheautomator.com/wp-content/uploads/2022/03/image-467.png) Showing files from a combo backup script for all databases in a single instance. ## Backing up Databases with Microsoft SSMS The SQL Server Management Studio tool is an equally viable option to perform backups like T-SQL and `sqlcmd` utility. You’ve already had a glimpse of how to navigate through the SSMS’s GUI in the previous examples, but this time, you’ll perform the backup directly in SSMS. 1\. Open Microsoft SSMS, right-click on the database to backup (**AdventureWorksLT2019**) —> **Tasks** —> **Back Up**, as shown below to initialize a backup task (step two). ![Creating a New Back Up Task](https://adamtheautomator.com/wp-content/uploads/2022/03/image-468.png) Creating a New Back Up Task 2\. Click on **Add** to select a backup folder on the Back Up Database window. > _You can also click on Remove to remove the default backup folder or leave it there so you can backup the same database in two locations._ ![Viewing Backup Up Database Window](https://adamtheautomator.com/wp-content/uploads/2022/03/image-469.png) Viewing Backup Up Database Window 3\. Click on the **File name** option, then the ellipsis button (**…**) to select a backup folder and set a backup name. But for this tutorial, the directory is set to _**C:\\ata\_db**_, and the backup name is set to **backup3\_AW.bak**. ![Adding the desired backup path and filename](https://adamtheautomator.com/wp-content/uploads/2022/03/image-470.png) Adding the desired backup path and filename 4\. Finally, click on **OK** to back up the selected database. > _You’d see two backup folders listed if you didn’t remove the default backup folder, as shown below._ ![Finalizing the Backup](https://adamtheautomator.com/wp-content/uploads/2022/03/image-471.png) Finalizing the Backup ## Backing up a Database with a Reusable SSMS Generated Script You’ve seen that backing up a database works perfectly fine using Microsoft SSMS. But, if you need a recurring backup command, Microsoft SSMS’s UI is not your best option. Instead, you can extract the SQL script from SSSM to perform the task. 1\. Initialize a backup as you did in step one of the “Backing up Databases with Microsoft SSMS” section. 2\. Select the arrow down button beside **Script**, select **Script Action to File**, and choose a location to save the script. You can name the script anything you prefer, but in this tutorial, the script is called _backup7.sql_. ![Generating the reusable SQL script for backing up a database.](https://adamtheautomator.com/wp-content/uploads/2022/03/image-472.png) Generating the reusable SQL script for backing up a database. For reference, the script generated by SSMS contains the code below ```sql BACKUP DATABASE [AdventureWorksLT2019] TO DISK N'C:\ata_db\backup3_AW.bak' WITH NOFORMAT, NOINIT, NAME = N'AdventureWorksLT2019-Full Database Backup', SKIP, NOREWIND, NOUNLOAD, STATS = 10 ``` 3\. Finally, run the following command to invoke the reusable generated script (`backup7.sql`). The script works similarly to the scripts in the previous examples. The only difference is auto-generated by SSMS, so you didn’t have to write the code for the script manually. sqlcmd -S localhost\\SQLEXPRESS -i C:\\ata\_db\\backup7.sql Invoking _backup7.sql_ script file will generate the backup file accordingly, as shown below. ![Confirming the backup file creation of backup3\_AW.bak file ](https://adamtheautomator.com/wp-content/uploads/2022/03/image-473.png) Confirming the backup file creation of backup3\_AW.bak file ## Conclusion In this tutorial, you learned a couple of methods to create SQL Server database backup scripts to backup your databases. You’ve learned to use Transact-SQL and Microsoft’s very own SQL Server Management Studio to perform backups, whether full or differential backups. At this point, you can now create your own SQL scripts and easily run backups for your databases. Now, how do you plan to incorporate this newfound knowledge into your admin tasks? Perhaps creating scheduled tasks with PowerShell to automate backups? Related:[Related: How to Set Up and Manage Scheduled Tasks with PowerShell](https://adamtheautomator.com/powershell-scheduled-task/) Share this article [Share on X](https://twitter.com/intent/tweet?url=https%3A%2F%2Fadamtheautomator.com%2Fsql-server-backup-database-script%2F&text=How%20to%20Create%20a%20Handy%20SQL%20Server%20Backup%20Database%20Script)[Share on Facebook](https://www.facebook.com/sharer/sharer.php?u=https%3A%2F%2Fadamtheautomator.com%2Fsql-server-backup-database-script%2F)[Share on LinkedIn](https://www.linkedin.com/sharing/share-offsite/?url=https%3A%2F%2Fadamtheautomator.com%2Fsql-server-backup-database-script%2F) ## Related Posts ![](https://adamtheautomator.com/wp-content/uploads/2025/04/featured-image.png) ### [Vibe Coding: How I Built a 120K Line App Without “Learning to Code”](/vibe-coding-with-ai/) Building real applications with AI isn't just for developers anymore. Here's how I went from PowerShell scripts to a full-stack React/Express app by embracing "vibe coding" with AI. ![](https://adamtheautomator.com/wp-content/uploads/2026/08/26572_featured_image.webp) ### [PowerShell Control Flow: A Practical Guide to Conditional Logic](/powershell-control-flow-guide/) Learn how to use PowerShell control flow including if statements, switch statements and conditional logic with practical real-world examples for server administration. ![](https://adamtheautomator.com/wp-content/uploads/2021/03/git-checkout-remote-branch.jpg) ### [Easily Perform Git Checkout Remote Branch \[Step-by-Step\]](/git-checkout-remote-branch/) Learn how Git remote branches work, effectively track remotes, and best practices to manage remotes and branches. ## Categories * [IT Ops](/category/it-ops/) * [Cloud](/category/cloud/) * [DevOps](/category/devops/) * [Home Ops](/category/home-ops/) * [Information Security](/category/infosec/) * [Software Development](/category/software-development/) ## Site * [Home](/) * [Tutorials](/tutorials/) * [Instructors](/author/) * [Advertising](/advertising/) * [Recommended Resources](/resources/) * [About Adam](/about-adam/) Copyright 2026© ATA Learning | [Privacy Policy](/privacy/)