Skip to content

Commit 8fcdc44

Browse files
authored
Added MSDB limitation explanation
1 parent b569bb3 commit 8fcdc44

File tree

1 file changed

+20
-0
lines changed

1 file changed

+20
-0
lines changed

articles/sql-database/sql-database-managed-instance-transact-sql-information.md

Lines changed: 20 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -531,6 +531,26 @@ The following variables, functions, and views return different results:
531531

532532
The maximum file size of `tempdb` can't be greater than 24 GB per core on a General Purpose tier. The maximum `tempdb` size on a Business Critical tier is limited by the instance storage size. `Tempdb` log file size is limited to 120 GB on General Purpose tier. Some queries might return an error if they need more than 24 GB per core in `tempdb` or if they produce more than 120 GB of log data.
533533

534+
### MSDB
535+
536+
The following MSDB schemas in managed instance must be owned by their respective predefined roles:
537+
538+
- General roles
539+
- TargetServersRole
540+
- [Fixed database roles](https://docs.microsoft.com/sql/ssms/agent/sql-server-agent-fixed-database-roles?view=sql-server-ver15)
541+
- SQLAgentUserRole
542+
- SQLAgentReaderRole
543+
- SQLAgentOperatorRole
544+
- [DatabaseMail roles](https://docs.microsoft.com/sql/relational-databases/database-mail/database-mail-configuration-objects?view=sql-server-ver15#DBProfile):
545+
- DatabaseMailUserRole
546+
- [Integration services roles](https://docs.microsoft.com/sql/integration-services/security/integration-services-roles-ssis-service?view=sql-server-ver15):
547+
- db_ssisadmin
548+
- db_ssisltduser
549+
- db_ssisoperator
550+
551+
> [!IMPORTANT]
552+
> Customers must not change the predefined role names, schema names and schema owners as such action will break the normal operation of a managed instance. In such occurrences SLAs cannot be guaranteed.
553+
534554
### Error logs
535555

536556
A managed instance places verbose information in error logs. There are many internal system events that are logged in the error log. Use a custom procedure to read error logs that filters out some irrelevant entries. For more information, see [managed instance – sp_readmierrorlog](https://blogs.msdn.microsoft.com/sqlcat/2018/05/04/azure-sql-db-managed-instance-sp_readmierrorlog/) or [managed instance extension(preview)](/sql/azure-data-studio/azure-sql-managed-instance-extension#logs) for Azure Data Studio.

0 commit comments

Comments
 (0)