Merge pull request #89324 from XiaoyuMSFT/supportability

large result set

Author: PRMerger9

articles/sql-data-warehouse/sql-data-warehouse-best-practices.md

@@ -58,6 +58,9 @@ INSERT, UPDATE, and DELETE statements run in a transaction and when they fail th
 
 See also [Understanding transactions][Understanding transactions], [Optimizing transactions][Optimizing transactions], [Table partitioning][Table partitioning], [TRUNCATE TABLE][TRUNCATE TABLE], [ALTER TABLE][ALTER TABLE], [Create table as select (CTAS)][Create table as select (CTAS)]
 
+## Reduce query result sizes  
+This helps you avoid client side issues caused by large query result.  You can edit your query to reduce the number of rows returned. Some query generation tools allow you to add “top N” syntax to each query.  You can also CETAS the query result to a temporary table and then use PolyBase export for the downlevel processing.
+
 ## Use the smallest possible column size
 When defining your DDL, using the smallest data type which will support your data will improve query performance.  This is especially important for CHAR and VARCHAR columns.  If the longest value in a column is 25 characters, then define your column as VARCHAR(25).  Avoid defining all character columns to a large default length.  In addition, define columns as VARCHAR when that is all that is needed rather than use NVARCHAR.