Merge pull request #27620 from rwestMSFT/rw-0706-fix-links

JamesJBarnett · web-flow · commit 30dce0fade97 · 2023-07-06T10:25:31.000-07:00
[SCOPED] Fix broken links and transct typo
diff --git a/.openpublishing.redirection.json b/.openpublishing.redirection.json
@@ -59812,7 +59812,7 @@
     },
     {
       "source_path": "docs/relational-databases/system-stored-procedures/sp-query-store-remove-plan-transct-sql.md",
-      "redirect_url": "/sql/relational-databases/sp-query-store-remove-plan-transact-sql",
+      "redirect_url": "/sql/relational-databases/system-stored-procedures/sp-query-store-remove-plan-transact-sql",
       "redirect_document_id": false
     },
     {
diff --git a/docs/relational-databases/in-memory-oltp/durability-for-memory-optimized-tables.md b/docs/relational-databases/in-memory-oltp/durability-for-memory-optimized-tables.md
@@ -19,7 +19,7 @@ ms.topic: conceptual
  All changes made to disk-based tables or durable memory-optimized tables are captured in one or more transaction log records. When a transaction commits, [!INCLUDE[ssNoVersion](../../includes/ssnoversion-md.md)] writes the log records associated with the transaction to disk before communicating to the application or user session that the transaction has committed. This guarantees that changes made by the transaction are durable. The transaction log for memory-optimized tables is fully integrated with the same log stream used by disk-based tables. This integration allows existing transaction log backup, recover, and restore operations to continue to work without requiring any additional steps. However, since [!INCLUDE[inmemory](../../includes/inmemory-md.md)] can increase transaction throughput of your workload significantly, log IO may become a performance bottleneck. To sustain this increased throughput, ensure the log IO subsystem can handle the increased load.  
   
 ## Data and Delta Files  
- The data in memory-optimized tables is stored as free-form data rows in an in-memory heap data structure, and are linked through one or more indexes in memory. There are no page structures for data rows, such as those used for disk-based tables. For long term persistence and to allow truncation of the transction log, operations on memory-optimized tables are persisted in a set of data and delta files. These files are generated based on the transaction log, using an asynchronous background process. The data and delta files are located in one or more containers (using the same mechanism used for FILESTREAM data). These containers are part of a memory-optimized filegroup.  
+ The data in memory-optimized tables is stored as free-form data rows in an in-memory heap data structure, and are linked through one or more indexes in memory. There are no page structures for data rows, such as those used for disk-based tables. For long term persistence and to allow truncation of the transaction log, operations on memory-optimized tables are persisted in a set of data and delta files. These files are generated based on the transaction log, using an asynchronous background process. The data and delta files are located in one or more containers (using the same mechanism used for FILESTREAM data). These containers are part of a memory-optimized filegroup.  
   
  Data is written to these files in a strictly sequential fashion, which minimizes disk latency for spinning media. You can use multiple containers on different disks to distribute the I/O activity. Data and delta files in multiple containers on different disks will increase database restore/recovery performance when data is read from the data and delta files on disk, into memory.  
   
diff --git a/docs/relational-databases/in-memory-oltp/estimate-memory-requirements-for-memory-optimized-tables.md b/docs/relational-databases/in-memory-oltp/estimate-memory-requirements-for-memory-optimized-tables.md
@@ -166,7 +166,7 @@ The number of extra rows can be estimated by computing the peak number of row up
   
 That value is then multiplied by the row size to get the number of bytes you need for row versioning.  
   
-`rowVersions = durationOfLongestTransctoinInSeconds * peakNumberOfRowUpdatesOrDeletesPerSecond`  
+`rowVersions = durationOfLongestTransactionInSeconds * peakNumberOfRowUpdatesOrDeletesPerSecond`  
   
 Memory needs for stale rows is then estimated by multiplying the number of stale rows by the size of a memory-optimized table row (See [Memory for the table](../../relational-databases/in-memory-oltp/estimate-memory-requirements-for-memory-optimized-tables.md#bkmk_MemoryForTable) above).  
   
diff --git a/docs/relational-databases/performance/monitoring-performance-by-using-the-query-store.md b/docs/relational-databases/performance/monitoring-performance-by-using-the-query-store.md
@@ -258,7 +258,7 @@ Stored procedures configure the Query Store.
 :::row-end:::
 :::row:::
     :::column:::
-        [sp_query_store_remove_plan (Transact-SQL)](../../relational-databases/system-stored-procedures/sp-query-store-remove-plan-transct-sql.md)
+        [sp_query_store_remove_plan (Transact-SQL)](../../relational-databases/system-stored-procedures/sp-query-store-remove-plan-transact-sql.md)
     :::column-end:::
     :::column:::
         [sp_query_store_remove_query (Transact-SQL)](../../relational-databases/system-stored-procedures/sp-query-store-remove-query-transact-sql.md)
diff --git a/docs/relational-databases/performance/using-the-query-store-with-in-memory-oltp.md b/docs/relational-databases/performance/using-the-query-store-with-in-memory-oltp.md
@@ -32,7 +32,7 @@ However, there are some specific aspects that users should be aware of when usin
   
 -   Queries and plans are captured and stored on the first native compilation and updated upon every recompilation.  
   
--   If you enabled Query Store or cleared its content after all native stored procedure were compiled you must recompile them manually in order to make them captured by the Query Store. The same applies if you removed queries manually by using [sp_query_store_remove_query &#40;Transact-SQL&#41;](../../relational-databases/system-stored-procedures/sp-query-store-remove-query-transact-sql.md) or [sp_query_store_remove_plan &#40;Transct-SQL&#41;](../../relational-databases/system-stored-procedures/sp-query-store-remove-plan-transct-sql.md). Use [sp_recompile &#40;Transact-SQL&#41;](../../relational-databases/system-stored-procedures/sp-recompile-transact-sql.md) to force procedure recompilation.  
+-   If you enabled Query Store or cleared its content after all native stored procedure were compiled you must recompile them manually in order to make them captured by the Query Store. The same applies if you removed queries manually by using [sp_query_store_remove_query &#40;Transact-SQL&#41;](../../relational-databases/system-stored-procedures/sp-query-store-remove-query-transact-sql.md) or [sp_query_store_remove_plan &#40;Transact-SQL&#41;](../../relational-databases/system-stored-procedures/sp-query-store-remove-plan-transact-sql.md). Use [sp_recompile &#40;Transact-SQL&#41;](../../relational-databases/system-stored-procedures/sp-recompile-transact-sql.md) to force procedure recompilation.  
   
 -   Query Store leverages plan generation mechanisms from in-memory OLTP to capture query execution plan during the compilation. Stored plan is semantically equivalent to one that you would get by using `SET SHOWPLAN_XML ON` with one difference; plans in Query Store are split and stored per individual statement.  
     
diff --git a/docs/relational-databases/system-functions/sys-fn-stmt-sql-handle-from-sql-stmt-transact-sql.md b/docs/relational-databases/system-functions/sys-fn-stmt-sql-handle-from-sql-stmt-transact-sql.md
@@ -86,7 +86,7 @@ JOIN sys.dm_exec_query_stats AS qs
   
 ## See Also  
  [sp_query_store_force_plan &#40;Transact-SQL&#41;](../../relational-databases/system-stored-procedures/sp-query-store-force-plan-transact-sql.md)   
- [sp_query_store_remove_plan &#40;Transct-SQL&#41;](../../relational-databases/system-stored-procedures/sp-query-store-remove-plan-transct-sql.md)   
+ [sp_query_store_remove_plan &#40;Transact-SQL&#41;](../../relational-databases/system-stored-procedures/sp-query-store-remove-plan-transact-sql.md)   
  [sp_query_store_unforce_plan &#40;Transact-SQL&#41;](../../relational-databases/system-stored-procedures/sp-query-store-unforce-plan-transact-sql.md)   
  [sp_query_store_reset_exec_stats &#40;Transact-SQL&#41;](../../relational-databases/system-stored-procedures/sp-query-store-reset-exec-stats-transact-sql.md)   
  [sp_query_store_flush_db &#40;Transact-SQL&#41;](../../relational-databases/system-stored-procedures/sp-query-store-flush-db-transact-sql.md)   
diff --git a/docs/t-sql/statements/create-table-as-clone-of-transact-sql.md b/docs/t-sql/statements/create-table-as-clone-of-transact-sql.md
@@ -17,7 +17,7 @@ monikerRange: "=fabric"
 
 Creates a new table as a zero-copy clone of another table in [!INCLUDE [fabric-dw](../../includes/fabric-dw.md)] in [!INCLUDE [fabric](../../includes/fabric.md)]. Only the metadata of the table is copied. The underlying data of the table, stored as parquet files, is not copied.
 
-For more information on cloning a table in [!INCLUDE [fabric](../../includes/fabric.md)], see [Clone table](/fabric/data-warehouse/clone-table-using-t-sql).
+For more information on cloning a table in [!INCLUDE [fabric](../../includes/fabric.md)], see [Clone table](/fabric/data-warehouse/tutorial-clone-table).
 
  :::image type="icon" source="../../includes/media/topic-link-icon.svg" border="false"::: [Transact-SQL syntax conventions](../../t-sql/language-elements/transact-sql-syntax-conventions-transact-sql.md)  
 
@@ -82,4 +82,4 @@ CREATE TABLE dbo.Employee AS CLONE OF dbo1.EmployeeUSA;
  
 - [Create a table on [!INCLUDE [fabric-dw](../../includes/fabric-dw.md)] in [!INCLUDE [fabric](../../includes/fabric.md)]](/fabric/data-warehouse/create-table)
 - [[!INCLUDE [fabric-dw](../../includes/fabric-dw.md)] in [!INCLUDE [fabric](../../includes/fabric.md)]](/fabric/data-warehouse/data-warehousing)
-- [Clone table in [!INCLUDE [fabric](../../includes/fabric.md)]](/fabric/data-warehouse/clone-table-using-t-sql)
+- [Clone table in [!INCLUDE [fabric](../../includes/fabric.md)]](/fabric/data-warehouse/tutorial-clone-table)

Original file line number	Diff line number	Diff line change
`@@ -59812,7 +59812,7 @@`
`59812`	`59812`	`},`
`59813`	`59813`	`{`
`59814`	`59814`	`"source_path": "docs/relational-databases/system-stored-procedures/sp-query-store-remove-plan-transct-sql.md",`
`59815`		`- "redirect_url": "/sql/relational-databases/sp-query-store-remove-plan-transact-sql",`
	`59815`	`+ "redirect_url": "/sql/relational-databases/system-stored-procedures/sp-query-store-remove-plan-transact-sql",`
`59816`	`59816`	`"redirect_document_id": false`
`59817`	`59817`	`},`
`59818`	`59818`	`{`