Skip to content

Commit af5e1f7

Browse files
authored
Merge pull request #12288 from MicrosoftDocs/master
10/02 PM Publish
2 parents ffb87aa + 24cccb3 commit af5e1f7

8 files changed

Lines changed: 174 additions & 76 deletions

File tree

docs/advanced-analytics/administration/resource-governor.md

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -3,7 +3,7 @@ title: Manage Python and R workloads with Resource Governor
33
description: Learn how to use Resource Governor to manage CPU, physical IO, and memory resources allocation for Python and R workloads in SQL Server Machine Learning Services.
44
ms.prod: sql
55
ms.technology: machine-learning
6-
ms.date: 10/01/2019
6+
ms.date: 10/02/2019
77
ms.topic: conceptual
88
author: dphansen
99
ms.author: davidph
@@ -25,11 +25,11 @@ For more general information, see [Resource Governor](../../relational-databases
2525

2626
By default, the external script runtimes for machine learning are limited to no more than 20% of total machine memory. It depends on your system, but in general, you might find this limit inadequate for serious machine learning tasks such as training a model or predicting on many rows of data.
2727

28-
## Use Resource Governor to control resourcing
28+
## Manage resources with Resource Governor
2929

3030
By default, external processes use up to 20% of total host memory on the local server. You can modify the default resource pool to make server-wide changes, with R and Python processes utilizing whatever capacity you make available to external processes.
3131

32-
Alternatively, you can construct custom *external resource pools*, with associated workload groups and classifiers, to determine resource allocation for requests originating from specific programs, hosts, or other criteria that you provide. An external resource pool is a type of resource pool introduced in [!INCLUDE[sssql15-md](../../includes/sssql15-md.md)] to help manage the R and Python processes external to the database engine.
32+
Alternatively, you can create custom **external resource pools**, with associated workload groups and classifiers, to determine resource allocation for requests originating from specific programs, hosts, or other criteria that you provide. An external resource pool is a type of resource pool introduced in [!INCLUDE[sssql15-md](../../includes/sssql15-md.md)] to help manage the R and Python processes external to the database engine.
3333

3434
1. [Enable resource governance](https://docs.microsoft.com/sql/relational-databases/resource-governor/enable-resource-governor) (it is off by default).
3535

docs/big-data-cluster/deployment-high-availability.md

Lines changed: 5 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -82,6 +82,11 @@ The following steps show how to create a patch file that includes these settings
8282
```bash
8383
azdata bdc config patch -c custom-aks/bdc.json --patch-file patch.json
8484
```
85+
1. Start cluster deployment using the cluster configuration profile created above
86+
87+
```bash
88+
azdata bdc create --config-profile custom-aks --accept-eula yes
89+
```
8590

8691
## Connect to SQL Server databases
8792

docs/database-engine/configure-windows/hybrid-buffer-pool.md

Lines changed: 2 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -89,6 +89,8 @@ SELECT name, is_memory_optimized_enabled FROM sys.databases;
8989

9090
When formatting your PMEM device on Windows, use the largest allocation unit size available for NTFS (2 MB in Windows Server 2019) and ensure the device has been formatted for DAX (Direct Access).
9191

92+
For optimal performance, enable [Locked Pages in Memory](./enable-the-lock-pages-in-memory-option-windows.md) on Windows.
93+
9294
Files sizes should be a multiple of 2 MB (modulo 2 MB should equal zero).
9395

9496
If the server scoped setting for Hybrid buffer pool is set to disabled, Hybrid buffer pool will not be used by any user database.

docs/relational-databases/data-tier-applications/delete-a-data-tier-application.md

Lines changed: 49 additions & 55 deletions
Original file line numberDiff line numberDiff line change
@@ -128,102 +128,96 @@ ms.author: "sstein"
128128

129129
[Using the Delete Data-tier Application Wizard](#UsingDeleteDACWizard)
130130

131-
## <a name="DeleteDACPowerShell"></a> Delete a DAC Using PowerShell
132-
**To delete a DAC using a PowerShell script**
131+
## <a name="DeleteDACPowerShell"></a> Using PowerShell
132+
133+
1. Create a SMO Server object and set it to the instance that contains the DAC to be deleted.
133134

134-
1. Create a SMO Server object and set it to the instance that contains the DAC to be deleted.
135+
1. Open a **ServerConnection** object and connect to the same instance.
135136

136-
2. Open a **ServerConnection** object and connect to the same instance.
137+
1. Use `add_DacActionStarted` and `add_DacActionFinished` to subscribe to the DAC upgrade events.
137138

138-
3. Use **add_DacActionStarted** and **add_DacActionFinished** to subscribe to the DAC upgrade events.
139+
1. Specify the DAC to delete.
139140

140-
4. Specify the DAC to delete.
141+
1. Use one of three examples, depending on which delete option is appropriate:
141142

142-
5. Use one of these three sets of code, depending on which delete option is appropriate:
143+
- To delete the DAC registration and leave the database intact, use the `Unmanage` method.
144+
- To delete the DAC registration and detach the database, use the `Uninstall` method and specify `DetachDatabase`.
145+
- To delete the DAC registration and drop the database, use the `Uninstall` method and specify `DropDatabase`.
143146

144-
- To delete the DAC registration but leave the database intact, use the **Unmanage()** method.
147+
### Delete the DAC and leave the database
148+
149+
The following example deletes a DAC named `<myApplication>` using the `Unmanage` method to delete the DAC but leave the database intact.
145150

146-
- To delete the DAC registration and detach the database, use the **Uninstall()** method and specify **DetachDatabase**.
147-
148-
- To delete the DAC registration and drop the database, use the **Uninstall()** method and specify **DropDatabase**.
149-
150-
### Example Deleting the DAC but Leaving the Database (PowerShell)
151-
The following example deletes a DAC named MyApplication using the **Unmanage()** method to delete the DAC but leave the database intact.
152-
153-
```
151+
```powershell
154152
## Set a SMO Server object to the default instance on the local computer.
155153
CD SQLSERVER:\SQL\localhost\DEFAULT
156-
$srv = get-item .
154+
$server = Get-Item .
157155
158156
## Open a Common.ServerConnection to the same instance.
159-
$serverconnection = New-Object Microsoft.SqlServer.Management.Common.ServerConnection($srv.ConnectionContext.SqlConnectionObject)
160-
$serverconnection.Connect()
161-
$dacstore = New-Object Microsoft.SqlServer.Management.Dac.DacStore($serverconnection)
157+
$serverConnection = New-Object Microsoft.SqlServer.Management.Common.ServerConnection($server.ConnectionContext.SqlConnectionObject)
158+
$serverConnection.Connect()
159+
$dacStore = New-Object Microsoft.SqlServer.Management.Dac.DacStore($serverConnection)
162160
163161
## Subscribe to the DAC delete events.
164-
$dacstore.add_DacActionStarted({Write-Host `n`nStarting at $(get-date) :: $_.Description})
165-
$dacstore.add_DacActionFinished({Write-Host Completed at $(get-date) :: $_.Description})
162+
$dacStore.add_DacActionStarted({Write-Host `n`nStarting at $(Get-Date) :: $_.Description})
163+
$dacStore.add_DacActionFinished({Write-Host Completed at $(Get-Date) :: $_.Description})
166164
167165
## Specify the DAC to delete.
168-
$dacName = "MyApplication"
166+
$dacName = "<myApplication>"
169167
170168
## Only delete the DAC definition from msdb, the associated database remains active.
171-
$dacstore.Unmanage($dacName)
172-
```
169+
$dacStore.Unmanage($dacName)
170+
```
173171

174-
[Delete a DAC Using PowerShell](#DeleteDACPowerShell)
172+
### Delete the DAC and detach the database
173+
174+
The following example deletes a DAC named `<myApplication>` using the `Uninstall` method to delete the DAC and detach the database.
175175

176-
### Example Deleting the DAC and Detaching the Database (PowerShell)
177-
The following example deletes a DAC named MyApplication using the **Uninstall()** method to delete the DAC and detach the database.
178-
179-
```
176+
```powershell
180177
## Set a SMO Server object to the default instance on the local computer.
181178
CD SQLSERVER:\SQL\localhost\DEFAULT
182-
$srv = get-item .
179+
$server = Get-Item .
183180
184181
## Open a Common.ServerConnection to the same instance.
185-
$serverconnection = New-Object Microsoft.SqlServer.Management.Common.ServerConnection($srv.ConnectionContext.SqlConnectionObject)
186-
$serverconnection.Connect()
187-
$dacstore = New-Object Microsoft.SqlServer.Management.Dac.DacStore($serverconnection)
182+
$serverConnection = New-Object Microsoft.SqlServer.Management.Common.ServerConnection($server.ConnectionContext.SqlConnectionObject)
183+
$serverConnection.Connect()
184+
$dacStore = New-Object Microsoft.SqlServer.Management.Dac.DacStore($serverConnection)
188185
189186
## Subscribe to the DAC delete events.
190-
$dacstore.add_DacActionStarted({Write-Host `n`nStarting at $(get-date) :: $_.Description})
191-
$dacstore.add_DacActionFinished({Write-Host Completed at $(get-date) :: $_.Description})
187+
$dacStore.add_DacActionStarted({Write-Host `n`nStarting at $(Get-Date) :: $_.Description})
188+
$dacStore.add_DacActionFinished({Write-Host Completed at $(Get-Date) :: $_.Description})
192189
193190
## Specify the DAC to delete.
194-
$dacName = "MyApplication"
191+
$dacName = "<myApplication>"
195192
196193
## Delete the DAC definition from msdb and detach the associated database.
197-
$dacstore.Uninstall($dacName, [Microsoft.SqlServer.Management.Dac.DacUninstallMode]::DetachDatabase)
198-
```
199-
200-
[Delete a DAC Using PowerShell](#DeleteDACPowerShell)
194+
$dacStore.Uninstall($dacName, [Microsoft.SqlServer.Management.Dac.DacUninstallMode]::DetachDatabase)
195+
```
201196

202-
### Example Deleting the DAC and Dropping the Database (PowerShell)
203-
The following example deletes a DAC named MyApplication using the **Uninstall()** method to delete the DAC and drop the database.
197+
### Delete the DAC and drop the database
198+
199+
The following example deletes a DAC named `<myApplication>` using the `Uninstall` method to delete the DAC and drop the database.
204200

205-
```
201+
```powershell
206202
## Set a SMO Server object to the default instance on the local computer.
207203
CD SQLSERVER:\SQL\localhost\DEFAULT
208-
$srv = get-item .
204+
$server = Get-Item .
209205
210206
## Open a Common.ServerConnection to the same instance.
211-
$serverconnection = New-Object Microsoft.SqlServer.Management.Common.ServerConnection($srv.ConnectionContext.SqlConnectionObject)
212-
$serverconnection.Connect()
213-
$dacstore = New-Object Microsoft.SqlServer.Management.Dac.DacStore($serverconnection)
207+
$serverConnection = New-Object Microsoft.SqlServer.Management.Common.ServerConnection($server.ConnectionContext.SqlConnectionObject)
208+
$serverConnection.Connect()
209+
$dacStore = New-Object Microsoft.SqlServer.Management.Dac.DacStore($serverConnection)
214210
215211
## Subscribe to the DAC delete events.
216-
$dacstore.add_DacActionStarted({Write-Host `n`nStarting at $(get-date) :: $_.Description})
217-
$dacstore.add_DacActionFinished({Write-Host Completed at $(get-date) :: $_.Description})
212+
$dacStore.add_DacActionStarted({Write-Host `n`nStarting at $(Get-Date) :: $_.Description})
213+
$dacStore.add_DacActionFinished({Write-Host Completed at $(Get-Date) :: $_.Description})
218214
219215
## Specify the DAC to delete.
220-
$dacName = "MyApplication"
216+
$dacName = "<myApplication>"
221217
222218
## Delete the DAC definition from msdb and drop the associated database.
223-
## $dacstore.Uninstall($dacName, [Microsoft.SqlServer.Management.Dac.DacUninstallMode]::DropDatabase)
224-
```
225-
226-
[Delete a DAC Using PowerShell](#DeleteDACPowerShell)
219+
$dacStore.Uninstall($dacName, [Microsoft.SqlServer.Management.Dac.DacUninstallMode]::DropDatabase)
220+
```
227221

228222
## See Also
229223
[Data-tier Applications](../../relational-databases/data-tier-applications/data-tier-applications.md)

docs/relational-databases/polybase/polybase-troubleshoot-connectivity.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -19,7 +19,7 @@ You can use interactive diagnostics that have been built into PolyBase to help t
1919

2020
This article serves as a guide to walk through the debugging process of such issues by leveraging these built-in diagnostics.
2121

22-
> [!TIP}
22+
> [!TIP]
2323
> Instead of following the steps in this guide, you can choose to run the [HDFS Kerberos Tester](https://github.com/microsoft/sql-server-samples/tree/master/samples/manage/hdfs-kerberos-tester) to troubleshoot HDFS Kerberos connections for PolyBase, when you experience HDFS Kerberos failure while creating an external table in a Kerberos secured HDFS cluster.
2424
> This tool will assist in ruling out non-SQL Server issues, to help you concentrate on resolving HDFS Kerberos setup issues, namely identifying issues with username/password misconfigurations, and cluster Kerberos setup misconfigurations.
2525
> This tool is completely independent from [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)]. It is available as a Jupyter Notebook and requires Azure Data Studio.

docs/t-sql/language-elements/if-else-transact-sql.md

Lines changed: 8 additions & 16 deletions
Original file line numberDiff line numberDiff line change
@@ -54,7 +54,7 @@ IF Boolean_expression
5454

5555
## Example
5656

57-
```
57+
```sql
5858
IF DATENAME(weekday, GETDATE()) IN (N'Saturday', N'Sunday')
5959
SELECT 'Weekend';
6060
ELSE
@@ -66,23 +66,20 @@ ELSE
6666
## Examples: [!INCLUDE[ssSDWfull](../../includes/sssdwfull-md.md)] and [!INCLUDE[ssPDW](../../includes/sspdw-md.md)]
6767
The following example uses `IF...ELSE` to determine which of two responses to show the user, based on the weight of an item in the `DimProduct` table.
6868

69-
```
69+
```sql
7070
-- Uses AdventureWorksDW
71-
71+
7272
DECLARE @maxWeight float, @productKey integer
7373
SET @maxWeight = 100.00
7474
SET @productKey = 424
75-
IF @maxWeight <= (SELECT Weight from DimProduct
76-
WHERE ProductKey = @productKey)
77-
(SELECT @productKey AS ProductKey, EnglishDescription, Weight,
78-
'This product is too heavy to ship and is only available for pickup.'
75+
IF @maxWeight <= (SELECT Weight from DimProduct WHERE ProductKey = @productKey)
76+
SELECT @productKey AS ProductKey, EnglishDescription, Weight, 'This product is too heavy to ship and is only available for pickup.'
7977
AS ShippingStatus
80-
FROM DimProduct WHERE ProductKey = @productKey);
78+
FROM DimProduct WHERE ProductKey = @productKey
8179
ELSE
82-
(SELECT @productKey AS ProductKey, EnglishDescription, Weight,
83-
'This product is available for shipping or pickup.'
80+
SELECT @productKey AS ProductKey, EnglishDescription, Weight, 'This product is available for shipping or pickup.'
8481
AS ShippingStatus
85-
FROM DimProduct WHERE ProductKey = @productKey);
82+
FROM DimProduct WHERE ProductKey = @productKey
8683
```
8784

8885
## See Also
@@ -93,8 +90,3 @@ ELSE
9390
[CASE &#40;Transact-SQL&#41;](../../t-sql/language-elements/case-transact-sql.md)
9491
[Control-of-Flow Language &#40;Transact-SQL&#41;](~/t-sql/language-elements/control-of-flow.md)
9592
[ELSE &#40;IF...ELSE&#41; &#40;Transact-SQL&#41;](../../t-sql/language-elements/else-if-else-transact-sql.md)
96-
97-
98-
99-
100-

0 commit comments

Comments
 (0)