Skip to content

Commit e143a39

Browse files
JamesJBarnettJamesJBarnett
authored
Merge pull request #23792 from MicrosoftDocs/MashaMSFT-patch-1
added limitations to sql agent jobs
2 parents a52ed40 + 346ae77 commit e143a39

1 file changed

Lines changed: 31 additions & 27 deletions

File tree

‎azure-sql/managed-instance/job-automation-managed-instance.md‎

Lines changed: 31 additions & 27 deletions
Original file line numberDiff line numberDiff line change
@@ -22,23 +22,6 @@ Using [SQL Server Agent](/sql/ssms/agent/sql-server-agent) in SQL Server and [SQ
2222
> [!Note]
2323
> SQL Agent is not available in Azure SQL Database or Azure Synapse Analytics. Instead, we recommend [Job automation with Elastic Jobs](../database/job-automation-overview.md).
2424
25-
### SQL Agent job limitations in SQL Managed Instance
26-
27-
It is worth noting the differences between SQL Agent available in SQL Server and as part of SQL Managed Instance. For more on the supported feature differences between SQL Server and SQL Managed Instance, see [Azure SQL Managed Instance T-SQL differences from SQL Server](./transact-sql-tsql-differences-sql-server.md#sql-server-agent).
28-
29-
Some of the SQL Agent features that are available in SQL Server are not supported in SQL Managed Instance:
30-
31-
- SQL Agent settings are read only.
32-
- The system stored procedure `sp_set_agent_properties` is not supported.
33-
- Enabling/disabling SQL Agent is currently not supported. SQL Agent is always running.
34-
- Notifications are partially supported:
35-
- Pager is not supported.
36-
- NetSend is not supported.
37-
- Alerts are not supported.
38-
- Proxies are not supported.
39-
- Eventlog is not supported.
40-
- Job schedule trigger based on an idle CPU is not supported.
41-
4225
## When to use SQL Agent jobs
4326

4427
There are several scenarios when you could use SQL Agent jobs:
@@ -69,7 +52,7 @@ There are several key concepts in SQL Agent Jobs:
6952
- **Schedules** define when the job should be executed.
7053
- **Notifications** enable you to define rules that will be used to notify operators via email once the job completes.
7154

72-
### SQL Agent job steps
55+
## Job steps
7356

7457
SQL Agent Job steps are sequences of actions that SQL Agent should execute. Every step has the following step that should be executed if the step succeeds or fails, number of retries in a case of failure.
7558

@@ -80,13 +63,11 @@ SQL Agent enables you to create different types of job steps, such as Transact-S
8063
8164
[Transactional replication](../managed-instance/replication-transactional-overview.md) can replicate the changes from your tables into other databases in SQL Managed Instance, Azure SQL Database, or SQL Server. For information, see [Configure replication in Azure SQL Managed Instance](./replication-between-two-instances-configure-tutorial.md).
8265

83-
Other types of job steps are not currently supported in SQL Managed Instance, including:
66+
Other types of job steps are **not currently supported** in SQL Managed Instance, such as Merge replication, and Queue reader.
67+
8468

85-
- Merge replication job step is not supported.
86-
- Queue Reader is not supported.
87-
- Analysis Services are not supported
8869

89-
### SQL Agent job schedules
70+
## Job schedules
9071

9172
A schedule specifies when a job runs. More than one job can run on the same schedule, and more than one schedule can apply to the same job.
9273

@@ -101,7 +82,7 @@ For more information on scheduling a SQL Agent job, see [Schedule a Job](/sql/ss
10182
> [!Note]
10283
> Azure SQL Managed Instance currently does not enable you to start a job when the CPU is idle.
10384
104-
### SQL Agent job notifications
85+
## Job notifications
10586

10687
SQL Agent jobs enable you to get notifications when the job finishes successfully or fails. You can receive notifications via email.
10788

@@ -182,13 +163,13 @@ EXEC msdb.dbo.sp_update_job @job_name=N'Load data using SSIS',
182163
@notify_email_operator_name=N'AzureSQLTeam';
183164
```
184165

185-
### SQL Agent job history
166+
## Job history
186167

187168
SQL Managed Instance currently doesn't allow you to change any SQL Agent properties because they are stored in the underlying registry values. This means options for adjusting the Agent retention policy for job history records are fixed at the default of 1000 total records and max 100 history records per job.
188169

189170
For more information, see [View SQL Agent job history](/sql/ssms/agent/view-the-job-history).
190171

191-
### SQL Agent fixed database role membership
172+
## Fixed database role membership
192173

193174
If users linked to non-sysadmin logins are added to any of the three SQL Agent fixed database roles in the `msdb` system database, there exists an issue in which explicit EXECUTE permissions need to be granted to three system stored procedures in the master database. If this issue is encountered, the error message "The EXECUTE permission was denied on the object <object_name> (Microsoft SQL Server, Error: 229)" will be shown.
194175

@@ -204,6 +185,29 @@ GRANT EXECUTE ON master.dbo.xp_sqlagent_is_starting TO [login_name];
204185
GRANT EXECUTE ON master.dbo.xp_sqlagent_notify TO [login_name];
205186
```
206187

188+
## SQL Agent job limitations in SQL Managed Instance
189+
190+
It is worth noting the differences between SQL Agent available in SQL Server and as part of SQL Managed Instance. For more on the supported feature differences between SQL Server and SQL Managed Instance, see [Azure SQL Managed Instance T-SQL differences from SQL Server](./transact-sql-tsql-differences-sql-server.md#sql-server-agent).
191+
192+
Some of the SQL Agent features that are available in SQL Server are not supported in SQL Managed Instance:
193+
194+
- SQL Agent settings are read only.
195+
- The system stored procedure `sp_set_agent_properties` is not supported.
196+
- Enabling/disabling SQL Agent is currently not supported. SQL Agent is always running.
197+
- While notifications are partially supported, the following are not supported:
198+
- Pager is not supported.
199+
- NetSend is not supported.
200+
- Alerts are not supported.
201+
- Proxies are not supported.
202+
- Eventlog is not supported.
203+
- Job schedule trigger based on an idle CPU is not supported.
204+
- Merge replication job steps are not supported.
205+
- Queue Reader is not supported.
206+
- Analysis Services is not supported.
207+
- Running a script stored as a file on disk is not supported.
208+
- Importing external modules, such as dbatools and dbachecks, are not supported.
209+
- PowerShell Core is not supported.
210+
207211
## Learn more
208212

209213
- [What is Azure SQL Managed Instance?](../managed-instance/sql-managed-instance-paas-overview.md)
@@ -215,4 +219,4 @@ GRANT EXECUTE ON master.dbo.xp_sqlagent_notify TO [login_name];
215219
## Next steps
216220

217221
- [Configure Database Mail](/sql/relational-databases/database-mail/configure-database-mail)
218-
- [Troubleshoot outbound SMTP connectivity problems in Azure](/azure/virtual-network/troubleshoot-outbound-smtp-connectivity)
222+
- [Troubleshoot outbound SMTP connectivity problems in Azure](/azure/virtual-network/troubleshoot-outbound-smtp-connectivity)

0 commit comments

Comments
 (0)