Skip to content

Commit f528bc8

Browse files
v-kentsv-kents
committed
Linkfix:SQL 2021-09) - 0
1 parent 7e3927c commit f528bc8

50 files changed

Lines changed: 67 additions & 102 deletions

File tree

Some content is hidden

Large Commits have some content hidden by default. Use the searchbox below for content that may be hidden.

‎docs/database-engine/configure-windows/register-a-service-principal-name-for-kerberos-connections.md‎

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -139,7 +139,7 @@ Manual intervention might be required to register or unregister the SPN if the s
139139

140140
To register the SPN manually, you can use Setspn tool that is built into Windows. Setspn.exe is a command-line tool that enables you to read, modify, and delete the Service Principal Names (SPN) directory property. This tool also enables you to view the current SPNs, reset the account's default SPNs, and add or delete supplemental SPNs.
141141

142-
For more information on the Setspn tool, required permissions and examples on how to use it, review [Setspn](https://docs.microsoft.com/previous-versions/windows/it-pro/windows-server-2012-R2-and-2012/cc731241(v=ws.11)).
142+
For more information on the Setspn tool, required permissions and examples on how to use it, review [Setspn](/previous-versions/windows/it-pro/windows-server-2012-R2-and-2012/cc731241(v=ws.11)).
143143

144144
The following example illustrates the syntax used to manually register an SPN for a TCP/IP connection using a domain user account:
145145

@@ -209,4 +209,4 @@ If SPN de-registration fails during shutdown, this failure is recorded in the SQ
209209
- [Service Principal Names (SPNs) in Client Connections (OLE DB)](../../relational-databases/native-client/ole-db/service-principal-names-spns-in-client-connections-ole-db.md)
210210
- [Service Principal Names (SPNs) in Client Connections (ODBC)](../../relational-databases/native-client/odbc/service-principal-names-spns-in-client-connections-odbc.md)
211211
- [SQL Server Native Client Features](../../relational-databases/native-client/features/sql-server-native-client-features.md)
212-
- [Manage Kerberos Authentication Issues in a Reporting Services Environment](/previous-versions/sql/sql-server-2008/ff679930(v=sql.100))
212+
- [Manage Kerberos Authentication Issues in a Reporting Services Environment](/previous-versions/sql/sql-server-2008/ff679930(v=sql.100))

‎docs/linux/tutorial-sql-server-containers-kubernetes-dh2i.md‎

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -364,7 +364,7 @@ DxEnterprise is high availability clustering software from DH2i that supports SQ
364364
With this, you should have an Always On availability group created and database(s) added to the group supporting high availability.
365365

366366
> [!NOTE]
367-
> You can deploy [basic Always On availability group](https://docs.microsoft.com/sql/database-engine/availability-groups/windows/basic-availability-groups-always-on-availability-groups) with SQL Server standard edition, but as you may be aware, one of the limitations of basic availability groups is that you are limited to only having two replicas and one additional configuration only replica required for successful automatic failover. Refer to the [documentation](https://docs.microsoft.com/sql/linux/sql-server-linux-availability-group-overview#configuration-only-replica-and-quorum) for more information on failover with configuration only replica. You can add configuration only replica for containers as well, and to do so, please refer to the [DH2i documentation](https://dh2i.com/wp-content/uploads/DxEnterprise-v21.0-Supplemental-Guide-for-Availability-Groups-in-Kubernetes.pdf), making sure to pass the availability mode in the 'dxcli add-ags-node' command as 'configuration_only'.
367+
> You can deploy [basic Always On availability group](../database-engine/availability-groups/windows/basic-availability-groups-always-on-availability-groups.md) with SQL Server standard edition, but as you may be aware, one of the limitations of basic availability groups is that you are limited to only having two replicas and one additional configuration only replica required for successful automatic failover. Refer to the [documentation](./sql-server-linux-availability-group-overview.md#configuration-only-replica-and-quorum) for more information on failover with configuration only replica. You can add configuration only replica for containers as well, and to do so, please refer to the [DH2i documentation](https://dh2i.com/wp-content/uploads/DxEnterprise-v21.0-Supplemental-Guide-for-Availability-Groups-in-Kubernetes.pdf), making sure to pass the availability mode in the 'dxcli add-ags-node' command as 'configuration_only'.
368368

369369

370370
## Steps to configure Always On availability group listener: (Optional)
@@ -373,7 +373,7 @@ You can also configure an Always On availability group listener; to do so, follo
373373

374374
1. Ensure you've created the AG listener using DxEnterprise as outlined in the optional step near the end of the [DH2i documentation](https://dh2i.com/wp-content/uploads/DxEnterprise-v21.0-Supplemental-Guide-for-Availability-Groups-in-Kubernetes.pdf).
375375
376-
2. In Kubernetes, you can optionally create static IP addresses. Creating static IP addresses ensures that if the listener service is deleted and recreated, the external IP address assigned to your listener service does not change and thus remains static. Follow the steps outlined [here](https://docs.microsoft.com/azure/aks/static-ip#create-a-static-ip-address) to create a static IP address in Azure Kubernetes Service (AKS).
376+
2. In Kubernetes, you can optionally create static IP addresses. Creating static IP addresses ensures that if the listener service is deleted and recreated, the external IP address assigned to your listener service does not change and thus remains static. Follow the steps outlined [here](/azure/aks/static-ip#create-a-static-ip-address) to create a static IP address in Azure Kubernetes Service (AKS).
377377
378378
3. After you have created an IP address, you assign that IP address and create the load balancer service, as shown in the sample yaml below:
379379
@@ -433,4 +433,4 @@ GO
433433
## Next steps
434434

435435
- [Deploy SQL Server containers on Azure Kubernetes Service](tutorial-sql-server-containers-kubernetes.md)
436-
- [Deploy SQL Server Read Scale AG on SQL Server Linux based containers deployed on kubernetes](https://techcommunity.microsoft.com/t5/sql-server/configure-sql-server-ag-read-scale-for-sql-containers-deployed/ba-p/2224742)
436+
- [Deploy SQL Server Read Scale AG on SQL Server Linux based containers deployed on kubernetes](https://techcommunity.microsoft.com/t5/sql-server/configure-sql-server-ag-read-scale-for-sql-containers-deployed/ba-p/2224742)

‎docs/machine-learning/python/reference/microsoftml/rx-fast-forest.md‎

Lines changed: 2 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -341,7 +341,7 @@ memory.
341341

342342
[Quantile regression forest](http://jmlr.org/papers/volume7/meinshausen06a/meinshausen06a.pdf)
343343

344-
[From Stumps to Trees to Forests](https://blogs.technet.microsoft.com/machinelearning/2014/09/10/from-stumps-to-trees-to-forests/)
344+
[From Stumps to Trees to Forests](/archive/blogs/machinelearning/from-stumps-to-trees-to-forests)
345345

346346

347347
## Binary classification example
@@ -498,5 +498,4 @@ Writing completed.
498498
2 320.0 16.6 73.0 23.421144
499499
3 187.0 5.1 87.0 80.662109
500500
4 175.0 7.4 89.0 67.570549
501-
```
502-
501+
```

‎docs/machine-learning/python/reference/microsoftml/rx-logistic-regression.md‎

Lines changed: 2 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -393,7 +393,7 @@ regression](https://en.wikipedia.org/wiki/Logistic_regression)
393393
Training of L1-Regularized Log-Linear Models](https://research.microsoft.com/apps/pubs/default.aspx?id=78900)
394394

395395
[Test Run - L1
396-
and L2 Regularization for Machine Learning](https://msdn.microsoft.com/magazine/dn904675.aspx)
396+
and L2 Regularization for Machine Learning](/archive/msdn-magazine/2015/february/test-run-l1-and-l2-regularization-for-machine-learning)
397397

398398

399399
## Binary classification example
@@ -558,5 +558,4 @@ Rows Read: 5, Total Rows Processed: 5, Total Chunk Time: 0.001 seconds
558558
2 setosa 0.756523 0.221933 0.021543
559559
3 setosa 0.767652 0.211191 0.021157
560560
4 versicolor 0.116369 0.498615 0.385016
561-
```
562-
561+
```

‎docs/machine-learning/python/reference/microsoftml/rx-oneclass-svm.md‎

Lines changed: 2 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -305,7 +305,7 @@ This algorithm is single-threaded and will always attempt to load the entire dat
305305

306306
[Wikipedia: Anomaly detection](https://en.wikipedia.org/wiki/Anomaly_detection)
307307

308-
[Microsoft Azure Machine Learning Studio (classic): One-Class Support Vector Machine](https://msdn.microsoft.com/library/azure/dn913103.aspx)
308+
[Microsoft Azure Machine Learning Studio (classic): One-Class Support Vector Machine](/azure/machine-learning/studio-module-reference/one-class-support-vector-machine)
309309

310310
[Estimating the Support of a High-Dimensional Distribution](https://research.microsoft.com/pubs/69731/tr-99-87.pdf)
311311

@@ -392,5 +392,4 @@ Writing completed.
392392
37 1.0 -0.189874
393393
38 0.0 0.635845
394394
39 0.0 0.555602
395-
```
396-
395+
```

‎docs/relational-databases/in-memory-oltp/blog-hardware-in-memory-oltp.md‎

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -19,7 +19,7 @@ In-Memory OLTP uses memory and disk in different ways than traditional disk-base
1919
> [!NOTE]
2020
> This article was a blog published on August 1, 2013, by the Microsoft SQL Server 2014 team. The blog webpage is being retired.
2121
>
22-
> [SQL Server In-Memory-OLTP](./in-memory-oltp-in-memory-optimization.md)
22+
> [SQL Server In-Memory-OLTP](./overview-and-usage-scenarios.md)
2323
2424
<!--
2525
Here was the link to the blog. This blog was captured into this new article on 2018/11/30, by GeneMi (MightyPen).

‎docs/relational-databases/in-memory-oltp/creating-and-managing-storage-for-memory-optimized-objects.md‎

Lines changed: 1 addition & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -59,6 +59,5 @@ monikerRange: "=azuresqldb-current||>=sql-server-2016||>=sql-server-linux-2017||
5959
- [Comparing Disk-Based Table Storage to Memory-Optimized Table Storage](../../relational-databases/in-memory-oltp/comparing-disk-based-table-storage-to-memory-optimized-table-storage.md)
6060

6161
## See Also
62-
[In-Memory OLTP &#40;In-Memory Optimization&#41;](../../relational-databases/in-memory-oltp/in-memory-oltp-in-memory-optimization.md)
63-
62+
[In-Memory OLTP &#40;In-Memory Optimization&#41;](./overview-and-usage-scenarios.md)
6463

‎docs/relational-databases/in-memory-oltp/demonstration-performance-improvement-of-in-memory-oltp.md‎

Lines changed: 1 addition & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -191,5 +191,4 @@ go
191191
```
192192

193193
## See Also
194-
[In-Memory OLTP &#40;In-Memory Optimization&#41;](../../relational-databases/in-memory-oltp/in-memory-oltp-in-memory-optimization.md)
195-
194+
[In-Memory OLTP &#40;In-Memory Optimization&#41;](./overview-and-usage-scenarios.md)

‎docs/relational-databases/in-memory-oltp/introduction-to-memory-optimized-tables.md‎

Lines changed: 2 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -97,9 +97,8 @@ EXECUTE AS CALLER has a small (approximately10%) performance hit caused by permi
9797

9898
## Scenarios
9999

100-
For a brief discussion of typical scenarios where [!INCLUDE[hek_1](../../includes/hek-1-md.md)] can improve performance, see [In-Memory OLTP](../../relational-databases/in-memory-oltp/in-memory-oltp-in-memory-optimization.md).
100+
For a brief discussion of typical scenarios where [!INCLUDE[hek_1](../../includes/hek-1-md.md)] can improve performance, see [In-Memory OLTP](./overview-and-usage-scenarios.md).
101101

102102
## See Also
103103

104-
[In-Memory OLTP &#40;In-Memory Optimization&#41;](../../relational-databases/in-memory-oltp/in-memory-oltp-in-memory-optimization.md)
105-
104+
[In-Memory OLTP &#40;In-Memory Optimization&#41;](./overview-and-usage-scenarios.md)

‎docs/relational-databases/in-memory-oltp/overview-and-usage-scenarios.md‎

Lines changed: 3 additions & 3 deletions
Original file line numberDiff line numberDiff line change
@@ -205,10 +205,10 @@ GO
205205

206206
- [In-Memory OLTP Technologies for Faster T-SQL Performance](./survey-of-initial-areas-in-in-memory-oltp.md)
207207
- Perf demo using In-Memory OLTP can be found at: [in-memory-oltp-perf-demo-v1.0](https://github.com/Microsoft/sql-server-samples/releases/tag/in-memory-oltp-demo-v1.0)
208-
- [17-minute video explaining In-Memory OLTP and showing the demo](in-memory-oltp-in-memory-optimization.md#anchorname-17minute-video)
208+
- [17-minute video explaining In-Memory OLTP and showing the demo](#anchorname-17minute-video)
209209
- [Script to enable In-Memory OLTP and set recommended options](https://github.com/microsoft/sql-server-samples/blob/master/samples/features/in-memory-database/in-memory-oltp/t-sql-scripts/enable-in-memory-oltp.sql)
210-
- [Main In-Memory OLTP documentation](in-memory-oltp-in-memory-optimization.md)
210+
- [Main In-Memory OLTP documentation]()
211211
- [Performance and resource utilization benefits of In-Memory OLTP in Azure SQL Database](https://azure.microsoft.com/blog/in-memory-oltp-in-azure-sql-database/)
212212
- [Improving temp table and table variable performance using memory optimization](/archive/blogs/sqlserverstorageengine/improving-temp-table-and-table-variable-performance-using-memory-optimization)
213213
- [Optimize Performance using In-Memory Technologies in SQL Database](/azure/sql-database/sql-database-in-memory)
214-
- [System-Versioned Temporal Tables with Memory-Optimized Tables](../tables/system-versioned-temporal-tables-with-memory-optimized-tables.md)
214+
- [System-Versioned Temporal Tables with Memory-Optimized Tables](../tables/system-versioned-temporal-tables-with-memory-optimized-tables.md)

0 commit comments

Comments
 (0)