You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
[!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)][!INCLUDE[ssSB](../../includes/sssb-md.md)] provides native support for messaging and queuing applications in the [!INCLUDE[ssDEnoversion](../../includes/ssdenoversion-md.md)]. This makes it easier for developers to create sophisticated applications that use the [!INCLUDE[ssDE](../../includes/ssde-md.md)] components to communicate between disparate databases. Developers can use [!INCLUDE[ssSB](../../includes/sssb-md.md)] to easily build distributed and reliable applications.
35
35
36
36
Application developers who use [!INCLUDE[ssSB](../../includes/sssb-md.md)] can distribute data workloads across several databases without programming complex communication and messaging internals. This reduces development and test work because [!INCLUDE[ssSB](../../includes/sssb-md.md)] handles the communication paths in the context of a conversation. It also improves performance. For example, front-end databases supporting Web sites can record information and send process intensive tasks to queue in back-end databases. [!INCLUDE[ssSB](../../includes/sssb-md.md)] ensures that all tasks are managed in the context of transactions to assure reliability and technical consistency.
The reference documentation for [!INCLUDE[ssSB](../../includes/sssb-md.md)] is included in the [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)] documentation. This reference documentation includes the following sections:
No significant changes are introduced in [!INCLUDE[ssCurrent](../../includes/sscurrent-md.md)]. The following changes were introduced in [!INCLUDE[ssSQL11](../../includes/sssql11-md.md)].
55
+
56
+
### Service broker and Azure SQL Database Managed Instance
57
+
58
+
- Cross-instance service broker is not supported
59
+
-`sys.routes` - Prerequisite: select address from sys.routes. Address must be LOCAL on every route. See [sys.routes](../../relational-databases/system-catalog-views/sys-routes-transact-sql.md).
60
+
-`CREATE ROUTE` - you cannot use `CREATE ROUTE` with `ADDRESS` other than `LOCAL`. See [CREATE ROUTE](https://docs.microsoft.com/sql/t-sql/statements/create-route-transact-sql).
61
+
-`ALTER ROUTE` cannot use `ALTER ROUTE` with `ADDRESS` other than `LOCAL`. See [ALTER ROUTE](../../t-sql/statements/alter-route-transact-sql.md).
57
62
58
63
### Messages can be sent to multiple target services (multicast)
59
64
The syntax of the [SEND (Transact-SQL)](../../t-sql/statements/send-transact-sql.md) statement has been extended to enable multicast by supporting multiple conversation handles.
<Token>**APPLIES TO:**SQL Server (starting with 2008) Azure SQL Database (Managed Instance only) Azure SQL Data Warehouse Parallel Data Warehouse </Token>
A *copy-only backup* is a [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] backup that is independent of the sequence of conventional [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] backups. Usually, taking a backup changes the database and affects how later backups are restored. However, occasionally, it is useful to take a backup for a special purpose without affecting the overall backup and restore procedures for the database. Copy-only backups serve this purpose.
> Azure SQL Database supports the **event_file** target, but only by using a blob in Azure Storage for the output. SQL Database cannot store event output in a file on your local harddrive.
154
+
> Azure SQL Database only supports storing `xel` files on Azure blob storage.
155
155
>
156
156
> For an **event_file** code example particular to SQL Database (and to SQL Database Managed Instance), see [Event File target code for extended events in SQL Database](https://docs.microsoft.com/azure/sql-database/sql-database-xevent-code-event-file).
|**server_id**|**int**|Local ID of linked server.|
39
-
|**name**|**sysname**|When **server_id** = 0, this is the server name.<br /><br /> When **server_id** >0 , this is the local name of linked server.|
40
-
|**product**|**sysname**|Product name of the linked server. "SQL Server" indicates this is another instance of [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)].|
37
+
|**name**|**sysname**|When **server_id** = 0, the returned value is the server name.<br /><br /> When **server_id** > 0, the returned value is the local name of linked server.|
38
+
|**product**|**sysname**|Product name of the linked server. A value of "SQL Server" indicates another instance of [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)].|
41
39
|**provider**|**sysname**|OLE DB provider name for connecting to linked server.|
42
40
|**data_source**|**nvarchar(4000)**|OLE DB data source connection property.|
43
41
|**location**|**nvarchar(4000)**|OLE DB location connection property. NULL if none.|
Permissions are not required to view the local server (**server_id** = 0).
68
66
69
-
When you create a linked or remote server, [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] creates a default login mapping to the **public** server role. This means that by default, all logins can view all linked and remote servers. To restrict visibility to these servers, remove the default login mapping by executing [sp_droplinkedsrvlogin](../../relational-databases/system-stored-procedures/sp-droplinkedsrvlogin-transact-sql.md) and specifying NULL for the *locallogin* parameter.
70
-
71
-
If the default login mapping is deleted, only users that have been explicitly added as a linked login or remote login can view the linked or remote servers for which they have a login. To view all linked and remote servers after the default login mapping is deleted requires the following permissions:
67
+
When you create a linked or remote server, [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] creates a default login mapping to the **public** server role. Default login mapping means that all logins can view all linked and remote servers. To restrict visibility to these servers, remove the default login mapping by executing [sp_droplinkedsrvlogin](../../relational-databases/system-stored-procedures/sp-droplinkedsrvlogin-transact-sql.md) and specifying NULL for the *locallogin* parameter.
72
68
73
-
- ALTER ANY LINKED SERVER or ALTER ANY LOGIN ON SERVER
69
+
If the default login mapping is deleted, only users that have been explicitly added as a linked login or remote login can view the linked or remote servers for which they have a login. The following permissions are required to view all linked and remote servers after the default login mapping:
74
70
75
-
- Membership in the **setupadmin** or **sysadmin** fixed server roles
71
+
-`ALTER ANY LINKED SERVER` or `ALTER ANY LOGIN ON SERVER`
72
+
- Membership in the **setupadmin** or **sysadmin** fixed server roles
> For database-level configuration options, see [ALTER DATABASE SCOPED CONFIGURATION (Transact-SQL)](../../t-sql/statements/alter-database-scoped-configuration-transact-sql.md). To configure Soft-NUMA, see [Soft-NUMA (SQL Server)](../../database-engine/configure-windows/soft-numa-sql-server.md).
![Topic link icon](../../database-engine/configure-windows/media/topic-link.gif"Topic link icon")[Transact-SQL Syntax Conventions](../../t-sql/language-elements/transact-sql-syntax-conventions-transact-sql.md)
Is the server to be removed. *server* is **sysname**, with no default. *server* must exist.
47
44
48
-
[**@droplogins =**]**'droplogins'** | NULL
49
-
Indicates that related remote and linked server logins for *server* must also be removed if **droplogins** is specified. **@droplogins** is **char(10)**, with a default of NULL.
45
+
*droplogins*
46
+
Indicates that related remote and linked server logins for *server* must also be removed if **droplogins** is specified. **`@droplogins`** is **char(10)**, with a default of NULL.
0 commit comments