Moved to include

Moved the warning to include rather than explicitly repeating every time

Author: peachdawnleach

src/current/_includes/common/sql/incremental-location-warning.md

@@ -0,0 +1,3 @@
+{{site.data.alerts.callout_danger}}
+The `incremental_location` parameter is deprecated in versions 25.4 and later. If needed, you can continue to work with already existing backups that use a custom `incremental_location` , but this ability will be removed in version 26.2.
+{{site.data.alerts.end}}

src/current/v23.1/alter-backup-schedule.md

@@ -154,9 +154,7 @@ Full backups are implicitly of `backup_type` `0`, and so does not display in the
 
 ### Apply different options to scheduled backups
 
-{{site.data.alerts.callout_danger}}
-The `incremental_location` parameter is deprecated in versions 25.4 and later. If needed, you can continue to work with already existing backups that use a custom `incremental_location` , but this ability will be removed in version 26.2.
-{{site.data.alerts.end}}
+{% include common/sql/incremental-location-warning.md %}
 
 You can modify the behavior of your backup schedule and the backup jobs with `SET SCHEDULE OPTION` and `SET WITH`. See the [Schedule options](#schedule-options) table and the [Backup options](#backup-options) table for a list of the available options.
 

src/current/v23.1/backup.md

@@ -308,9 +308,7 @@ See [Name Resolution]({% link {{ page.version.version }}/sql-name-resolution.md
 
 ### Create incremental backups
 
-{{site.data.alerts.callout_danger}}
-The `incremental_location` parameter is deprecated in versions 25.4 and later. If needed, you can continue to work with already existing backups that use a custom `incremental_location` , but this ability will be removed in version 26.2.
-{{site.data.alerts.end}}
+{% include common/sql/incremental-location-warning.md %}
 
 When a `BACKUP` statement specifies an existing subdirectory in the collection, explicitly or via the `LATEST` keyword, an incremental backup will be added to the default `/incrementals` directory at the root of the [collection]({% link {{ page.version.version }}/take-full-and-incremental-backups.md %}#backup-collections) storage location.
 

src/current/v23.1/restore.md

@@ -572,9 +572,7 @@ After it's restored into a new database, you can write the restored `users` tabl
 
 #### Restore from incremental backups in a different location
 
-{{site.data.alerts.callout_danger}}
-The `incremental_location` parameter is deprecated in versions 25.4 and later. If needed, you can continue to work with already existing backups that use a custom `incremental_location` , but this ability will be removed in version 26.2.
-{{site.data.alerts.end}}
+{% include common/sql/incremental-location-warning.md %}
 
 To restore an incremental backup that was taken using the [`incremental_location` option]({% link {{ page.version.version }}/backup.md %}#incr-location), you must run the `RESTORE` statement with both:
 

src/current/v23.1/take-and-restore-locality-aware-backups.md

@@ -164,9 +164,7 @@ There is different syntax for taking an incremental backup depending on where yo
 
 	For more detail on using the `incremental_location` option, see [Incremental backups with explicitly specified destinations]({% link {{ page.version.version }}/take-full-and-incremental-backups.md %}#incremental-backups-with-explicitly-specified-destinations).
 
-	{{site.data.alerts.callout_danger}}
-	The `incremental_location` parameter is deprecated in versions 25.4 and later. If needed, you can continue to work with already existing backups that use a custom `incremental_location` , but this ability will be removed in version 26.2.
-	{{site.data.alerts.end}}
+	{% include common/sql/incremental-location-warning.md %}
 
 ## Restore from an incremental locality-aware backup
 

src/current/v23.1/take-full-and-incremental-backups.md

@@ -220,9 +220,7 @@ RESTORE FROM '2023/03/23-213101.37' IN 's3://bucket/path?AUTH=implicit';
 
 ### Incremental backups with explicitly specified destinations
 
-{{site.data.alerts.callout_danger}}
-The `incremental_location` parameter is deprecated in versions 25.4 and later. If needed, you can continue to work with already existing backups that use a custom `incremental_location` , but this ability will be removed in version 26.2.
-{{site.data.alerts.end}}
+{% include common/sql/incremental-location-warning.md %}
 
 To explicitly control where your incremental backups go, use the [`incremental_location`]({% link {{ page.version.version }}/backup.md %}#options) option. By default, incremental backups are stored in the `/incrementals` subdirectory at the root of the collection. However, there are some advanced cases where you may want to store incremental backups in a different storage location.
 

src/current/v23.2/alter-backup-schedule.md

@@ -154,9 +154,7 @@ Full backups are implicitly of `backup_type` `0`, and so does not display in the
 
 ### Apply different options to scheduled backups
 
-{{site.data.alerts.callout_danger}}
-The `incremental_location` parameter is deprecated in versions 25.4 and later. If needed, you can continue to work with already existing backups that use a custom `incremental_location` , but this ability will be removed in version 26.2.
-{{site.data.alerts.end}}
+{% include common/sql/incremental-location-warning.md %}
 
 You can modify the behavior of your backup schedule and the backup jobs with `SET SCHEDULE OPTION` and `SET WITH`. See the [Schedule options](#schedule-options) table and the [Backup options](#backup-options) table for a list of the available options.
 

src/current/v23.2/backup.md

@@ -306,9 +306,7 @@ See [Name Resolution]({% link {{ page.version.version }}/sql-name-resolution.md
 
 ### Create incremental backups
 
-{{site.data.alerts.callout_danger}}
-The `incremental_location` parameter is deprecated in versions 25.4 and later. If needed, you can continue to work with already existing backups that use a custom `incremental_location` , but this ability will be removed in version 26.2.
-{{site.data.alerts.end}}
+{% include common/sql/incremental-location-warning.md %}
 
 When a `BACKUP` statement specifies an existing subdirectory in the collection, explicitly or via the `LATEST` keyword, an incremental backup will be added to the default `/incrementals` directory at the root of the [collection]({% link {{ page.version.version }}/take-full-and-incremental-backups.md %}#backup-collections) storage location.
 

src/current/v23.2/restore.md

@@ -570,9 +570,7 @@ After it's restored into a new database, you can write the restored `users` tabl
 
 #### Restore from incremental backups in a different location
 
-{{site.data.alerts.callout_danger}}
-The `incremental_location` parameter is deprecated in versions 25.4 and later. If needed, you can continue to work with already existing backups that use a custom `incremental_location` , but this ability will be removed in version 26.2.
-{{site.data.alerts.end}}
+{% include common/sql/incremental-location-warning.md %}
 
 To restore an incremental backup that was taken using the [`incremental_location` option]({% link {{ page.version.version }}/backup.md %}#incr-location), you must run the `RESTORE` statement with both:
 

src/current/v23.2/take-and-restore-locality-aware-backups.md

@@ -164,9 +164,7 @@ There is different syntax for taking an incremental backup depending on where yo
 
 	For more detail on using the `incremental_location` option, see [Incremental backups with explicitly specified destinations]({% link {{ page.version.version }}/take-full-and-incremental-backups.md %}#incremental-backups-with-explicitly-specified-destinations).
 
-	{{site.data.alerts.callout_danger}}
-	The `incremental_location` parameter is deprecated in versions 25.4 and later. If needed, you can continue to work with already existing backups that use a custom `incremental_location` , but this ability will be removed in version 26.2.
-	{{site.data.alerts.end}}
+	{% include common/sql/incremental-location-warning.md %}
 
 ## Restore from an incremental locality-aware backup