Lokasi ngalangkungan proxy:   [ UP ]  
[Ngawartoskeun bug]   [Panyetelan cookie]                
Skip to content

Commit 67f95fb

Browse files
authored
Merge pull request #1202 from v-thepet/fix-azure-note
fix azure notes
2 parents 671d3ae + cce86a4 commit 67f95fb

4 files changed

Lines changed: 10 additions & 5 deletions

File tree

docs/relational-databases/extended-events/advanced-viewing-of-target-data-from-extended-events-in-sql-server.md

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -137,7 +137,8 @@ The target data is displayed in a tabbed pane in SSMS. This is shown in the foll
137137
![your target > View Target Data](../../relational-databases/extended-events/media/xevents-ssms-ui20-viewtargetdata.png)
138138

139139

140-
> [AZURE.NOTE] **View Target Data** displays the *accumulated data from multiple .XEL files* from the given event session. Each **Start**-**Stop** cycle creates a file with a later time-derived integer embedded in its name, but each file shares the same root name.
140+
> [!NOTE]
141+
> **View Target Data** displays the *accumulated data from multiple .XEL files* from the given event session. Each **Start**-**Stop** cycle creates a file with a later time-derived integer embedded in its name, but each file shares the same root name.
141142
142143

143144

docs/relational-databases/in-memory-oltp/hash-indexes-for-memory-optimized-tables.md

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -173,7 +173,8 @@ Too *many* buckets has the following drawbacks:
173173
- Empty buckets use memory, though each bucket uses only 8 bytes.
174174

175175

176-
> [AZURE.NOTE] Adding more buckets does nothing to reduce the chaining together of entries that share a duplicate value. The rate of value duplication is used to decide whether a hash is the appropriate index type, not to calculate the bucket count.
176+
> [!NOTE]
177+
> Adding more buckets does nothing to reduce the chaining together of entries that share a duplicate value. The rate of value duplication is used to decide whether a hash is the appropriate index type, not to calculate the bucket count.
177178
178179

179180

docs/relational-databases/in-memory-oltp/survey-of-initial-areas-in-in-memory-oltp.md

Lines changed: 2 additions & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -77,7 +77,8 @@ The present article focuses on OLTP, and not on Analytics. For information on ho
7777
- [Columnstore Indexes Guide](../../relational-databases/indexes/columnstore-indexes-overview.md)
7878

7979

80-
> [AZURE.NOTE] A two minute video about the In-Memory features is available at [Azure SQL Database - In-Memory Technologies](http://channel9.msdn.com/Blogs/Windows-Azure/Azure-SQL-Database-In-Memory-Technologies). The video is dated December 2015.
80+
> [!NOTE]
81+
> A two minute video about the In-Memory features is available at [Azure SQL Database - In-Memory Technologies](http://channel9.msdn.com/Blogs/Windows-Azure/Azure-SQL-Database-In-Memory-Technologies). The video is dated December 2015.
8182
8283

8384
### Columnstore

docs/t-sql/statements/create-table-as-select-azure-sql-data-warehouse.md

Lines changed: 4 additions & 2 deletions
Original file line numberDiff line numberDiff line change
@@ -457,7 +457,8 @@ AS SELECT * FROM ClickStreamExt
457457

458458
Use CTAS to work around some unsupported features. Besides being able to run your code on the data warehouse, rewriting existing code to use CTAS will usually improve performance. This is a result of its fully parallelized design.
459459

460-
> [AZURE.NOTE] Try to think "CTAS first". If you think you can solve a problem using `CTAS` then that is generally the best way to approach it - even if you are writing more data as a result.
460+
> [!NOTE]
461+
> Try to think "CTAS first". If you think you can solve a problem using `CTAS` then that is generally the best way to approach it - even if you are writing more data as a result.
461462
>
462463
463464
<a name="ctas-replace-select-into-bk"></a>
@@ -716,7 +717,8 @@ Note the following:
716717
- ISNULL is the outermost function
717718
- The second part of the ISNULL is a constant i.e. 0
718719

719-
> [AZURE.NOTE] For the nullability to be correctly set it is vital to use `ISNULL` and not `COALESCE`. `COALESCE` is not a deterministic function and so the result of the expression will always be NULLable. `ISNULL` is different. It is deterministic. Therefore when the second part of the `ISNULL` function is a constant or a literal then the resulting value will be NOT NULL.
720+
> [!NOTE]
721+
> For the nullability to be correctly set it is vital to use `ISNULL` and not `COALESCE`. `COALESCE` is not a deterministic function and so the result of the expression will always be NULLable. `ISNULL` is different. It is deterministic. Therefore when the second part of the `ISNULL` function is a constant or a literal then the resulting value will be NOT NULL.
720722
721723
This tip is not just useful for ensuring the integrity of your calculations. It is also important for table partition switching. Imagine you have this table defined as your fact:
722724

0 commit comments

Comments
 (0)