Skip to content

Commit 61673a9

Browse files
committed
Update select_data_type.md
1 parent 415f59c commit 61673a9

File tree

1 file changed

+1
-1
lines changed

1 file changed

+1
-1
lines changed

docs/best-practices/select_data_type.md

Lines changed: 1 addition & 1 deletion
Original file line numberDiff line numberDiff line change
@@ -98,7 +98,7 @@ By applying our early simple rules to our posts table, we can identify an optima
9898
| `CommunityOwnedDate` | No | 2008-08-12 04:59:35.017000000, 2024-04-01 05:36:41.380000000 | - | Yes | Consider default 1970-01-01 for Nulls. Millisecond granularity is not required, use DateTime | DateTime |
9999
| `ClosedDate` | No | 2008-09-04 20:56:44, 2024-04-06 18:49:25.393000000 | - | Yes | Consider default 1970-01-01 for Nulls. Millisecond granularity is not required, use DateTime | DateTime |
100100

101-
:::note tip
101+
:::note Tip
102102
Identifying the type for a column relies on understanding its numeric range and number of unique values. To find the range of all columns, and the number of distinct values, users can use the simple query `SELECT * APPLY min, * APPLY max, * APPLY uniq FROM table FORMAT Vertical`. We recommend performing this over a smaller subset of the data as this can be expensive.
103103
:::
104104

0 commit comments

Comments
 (0)