Skip to content

Commit 93d3256

Browse files
committed
fix names
1 parent 086e0f7 commit 93d3256

File tree

5 files changed

+4
-4
lines changed

5 files changed

+4
-4
lines changed

articles/sql-data-warehouse/TOC.yml

Lines changed: 2 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -130,15 +130,15 @@
130130
- name: Materialized view
131131
items:
132132
- name: Performance tuning guidance
133-
href: sql-data-warehouse-performance-tuning-with-materialized-views.md
133+
href: performance-tuning-materialized-views.md
134134
- name: Create
135135
href: /sql/t-sql/statements/create-materialized-view-as-select-transact-sql
136136
- name: Alter
137137
href: /sql/t-sql/statements/alter-materialized-view-transact-sql
138138
- name: Ordered clustered columnstore index
139139
items:
140140
- name: Performance tuning guidance
141-
href: sql-data-warehouse-performance-tuning-with-ordered-CCI.md
141+
href: performance-tuning-ordered-CCI.md
142142
- name: Result set caching
143143
href: /sql/t-sql/statements/set-result-set-caching-transact-sql
144144
- name: Tables
18.3 KB
Loading
15.5 KB
Loading

articles/sql-data-warehouse/performance-tuning-materialized-views.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -337,7 +337,7 @@ GROUP BY c_customer_id
337337
```
338338
Check the execution plan of the original query again. Now the number of joins changes from 17 to 5 and there's no shuffle anymore. Click the Filter operation icon in the plan, its Output List shows the data is read from the materialized views instead of base tables.
339339

340-
![Plan_Output_List_with_Materialized_Views](media/performance-tuning-materialized-views/output_list.png)
340+
![Plan_Output_List_with_Materialized_Views](media/performance-tuning-materialized-views/output-list.png)
341341

342342
With materialized views, the same query runs much faster without any code change.
343343

articles/sql-data-warehouse/performance-tuning-ordered-cci.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -42,7 +42,7 @@ The performance of data loading into an ordered CCI table is similar to data loa
4242
Loading data into an ordered CCI table can take more time than data loading into a non-ordered CCI table because of the data sorting.
4343

4444
Here is an example performance comparison of loading data into tables with different schemas.
45-
![Performance_comparison_data_loading](media/performance-tuning-ordered-cci/cci_data_loading_performance.png)
45+
![Performance_comparison_data_loading](media/performance-tuning-ordered-cci/cci-data-loading-performance.png)
4646

4747
## Reduce segment overlapping
4848
Below are options to further reduce segment overlapping when creating ordered CCI on a new table via CTAS or on an existing table with data:

0 commit comments

Comments
 (0)