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
Copy file name to clipboardExpand all lines: docs/includes/sql-linux-quickstart-connect-query.md
+6-8Lines changed: 6 additions & 8 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -106,8 +106,8 @@ After installing SQL Server on Linux, review the best practices for configuring
106
106
107
107
In addition to **sqlcmd**, you can use the following cross-platform tools to manage SQL Server:
108
108
109
-
|||
110
-
|---|---|
109
+
| Tool | Description |
110
+
|---- |----------- |
111
111
|[Azure Data Studio](../azure-data-studio/index.yml)| A cross-platform GUI database management utility. |
112
112
|[Visual Studio Code](../linux/sql-server-linux-develop-use-vscode.md)| A cross-platform GUI code editor that run Transact-SQL statements with the mssql extension. |
113
113
|[PowerShell Core](../linux/sql-server-linux-manage-powershell-core.md)| A cross-platform automation and configuration tool based on cmdlets. |
@@ -129,12 +129,10 @@ For other tools that run on Windows but connect to SQL Server on Linux, see:
129
129
130
130
For other installation scenarios, see the following resources:
131
131
132
-
|||
133
-
|---|---|
134
-
|[Upgrade](../linux/sql-server-linux-setup.md#upgrade)| Learn how to upgrade an existing installation of SQL Server on Linux |
135
-
|[Uninstall](../linux/sql-server-linux-setup.md#uninstall)| Uninstall SQL Server on Linux |
136
-
|[Unattended install](../linux/sql-server-linux-setup.md#unattended)| Learn how to script the installation without prompts |
137
-
|[Offline install](../linux/sql-server-linux-setup.md#offline)| Learn how to manually download the packages for offline installation |
132
+
*[Upgrade](../linux/sql-server-linux-setup.md#upgrade): Learn how to upgrade an existing installation of SQL Server on Linux
133
+
*[Uninstall](../linux/sql-server-linux-setup.md#uninstall): Uninstall SQL Server on Linux
134
+
*[Unattended install](../linux/sql-server-linux-setup.md#unattended): Learn how to script the installation without prompts
135
+
*[Offline install](../linux/sql-server-linux-setup.md#offline): Learn how to manually download the packages for offline installation
138
136
139
137
> [!TIP]
140
138
> For answers to frequently asked questions, see the [SQL Server on Linux FAQ](../linux/sql-server-linux-faq.md).
A synonym is a database object that serves the following purposes:
22
22
23
23
- Provides an alternative name for another database object, referred to as the base object, that can exist on a local or remote server.
@@ -29,17 +29,37 @@ For example, consider the **Employee** table of [!INCLUDE[ssSampleDBCoShort](../
29
29
To address both these issues, you can create a synonym, **EmpTable**, on **Server2** for the **Employee** table on **Server1**. Now, the client application only has to use the single-part name, **EmpTable**, to reference the **Employee** table. Also, if the location of the **Employee** table changes, you will have to modify the synonym, **EmpTable**, to point to the new location of the **Employee** table. Because there is no ALTER SYNONYM statement, you first have to drop the synonym, **EmpTable**, and then re-create the synonym with the same name, but point the synonym to the new location of **Employee**.
30
30
31
31
A synonym belongs to a schema, and like other objects in a schema, the name of a synonym must be unique. You can create synonyms for the following database objects:
> Four-part names for function base objects are not supported.
@@ -57,23 +77,48 @@ If you have a default schema that you do not own and want to create a synonym, y
57
77
Only synonym owners, members of **db_owner**, or members of **db_ddladmin** can grant permission on a synonym.
58
78
59
79
You can `GRANT`, `DENY`, and `REVOKE` all or any of the following permissions on a synonym:
60
-
61
-
|||
62
-
|-|-|
63
-
|CONTROL|DELETE|
64
-
|EXECUTE|INSERT|
65
-
|SELECT|TAKE OWNERSHIP|
66
-
|UPDATE|VIEW DEFINITION|
67
-
80
+
81
+
:::row:::
82
+
:::column:::
83
+
CONTROL
84
+
85
+
EXECUTE
86
+
87
+
SELECT
88
+
89
+
UPDATE
90
+
:::column-end:::
91
+
:::column:::
92
+
DELETE
93
+
94
+
INSERT
95
+
96
+
TAKE OWNERSHIP
97
+
98
+
VIEW DEFINITION
99
+
:::column-end:::
100
+
:::row-end:::
101
+
68
102
## Using Synonyms
69
-
You can use synonyms in place of their referenced base object in several SQL statements and expression contexts. The following table contains a list of these statements and expression contexts:
70
-
71
-
|||
72
-
|-|-|
73
-
|SELECT|INSERT|
74
-
|UPDATE|DELETE|
75
-
|EXECUTE|Sub-selects|
76
-
103
+
You can use synonyms in place of their referenced base object in several SQL statements and expression contexts. The following columns contain a list of these statements and expression contexts:
104
+
105
+
:::row:::
106
+
:::column:::
107
+
SELECT
108
+
109
+
UPDATE
110
+
111
+
EXECUTE
112
+
:::column-end:::
113
+
:::column:::
114
+
INSERT
115
+
116
+
DELETE
117
+
118
+
Sub-selects
119
+
:::column-end:::
120
+
:::row-end:::
121
+
77
122
When you are working with synonyms in the contexts previously stated, the base object is affected. For example, if a synonym references a base object that is a table and you insert a row into the synonym, you are actually inserting a row into the referenced table.
The following permission statements are associated only with the synonym and not the base object:
94
-
95
-
|||
96
-
|-|-|
97
-
|GRANT|DENY|
98
-
|REVOKE||
99
-
139
+
140
+
:::row:::
141
+
:::column:::
142
+
GRANT
143
+
144
+
REVOKE
145
+
:::column-end:::
146
+
:::column:::
147
+
DENY
148
+
:::column-end:::
149
+
:::row-end:::
150
+
100
151
Synonyms are not schema-bound and, therefore, cannot be referenced by the following schema-bound expression contexts:
101
-
102
-
|||
103
-
|-|-|
104
-
|CHECK constraints|Computed columns|
105
-
|Default expressions|Rule expressions|
106
-
|Schema-bound views|Schema-bound functions|
152
+
153
+
:::row:::
154
+
:::column:::
155
+
CHECK constraints
156
+
157
+
Default expressions
158
+
159
+
Schema-bound views
160
+
:::column-end:::
161
+
:::column:::
162
+
Computed columns
163
+
164
+
Rule expressions
165
+
166
+
Schema-bound functions
167
+
:::column-end:::
168
+
:::row-end:::
107
169
108
170
For more information about schema-bound functions, see [Create User-defined Functions (Database Engine)](../../relational-databases/user-defined-functions/create-user-defined-functions-database-engine.md).
Copy file name to clipboardExpand all lines: docs/relational-databases/system-catalog-views/always-on-availability-groups-catalog-views-transact-sql.md
+21-9Lines changed: 21 additions & 9 deletions
Display the source diff
Display the rich diff
Original file line number
Diff line number
Diff line change
@@ -17,21 +17,33 @@ author: CarlRabeler
17
17
ms.author: carlrab
18
18
---
19
19
# Always On Availability Groups Catalog Views (Transact-SQL)
> For information about joined availability databases, see the **replica_id** and **group_database_id** columns in [sys.databases (Transact-SQL);](../../relational-databases/system-catalog-views/sys-databases-transact-sql.md).
46
+
> For information about joined availability databases, see the **replica_id** and **group_database_id** columns in [sys.databases (Transact-SQL);](../../relational-databases/system-catalog-views/sys-databases-transact-sql.md).
0 commit comments