Merge pull request #22161 from MikeRayMSFT/20220520-copy-into

Update for parquet files

Author: MikeRayMSFT

azure-sql/database/firewall-configure.md

@@ -31,10 +31,13 @@ Connection attempts from the internet and Azure must pass through the firewall b
 
 ### Server-level IP firewall rules
 
-These rules enable clients to access your entire server, that is, all the databases managed by the server. The rules are stored in the *master* database. You can have a maximum of 128 server-level IP firewall rules for a server. If you have the **Allow Azure Services and resources to access this server** setting enabled, this counts as a single firewall rule for the server.
+These rules enable clients to access your entire server, that is, all the databases managed by the server. The rules are stored in the *master* database. The default value is up to 256 server-level IP firewall rules for a server. If you have the **Allow Azure Services and resources to access this server** setting enabled, this counts as a single firewall rule for the server.
 
 You can configure server-level IP firewall rules by using the Azure portal, PowerShell, or Transact-SQL statements.
 
+> [!NOTE]
+> The maximum number of server-level IP firewall rules is limited to 128 when configuring using the Azure portal.
+
 - To use the portal or PowerShell, you must be the subscription owner or a subscription contributor.
 - To use Transact-SQL, you must connect to the *master* database as the server-level principal login or as the Azure Active Directory administrator. (A server-level IP firewall rule must first be created by a user who has Azure-level permissions.)
 
@@ -47,7 +50,7 @@ Database-level IP firewall rules enable clients to access certain (secure) datab
 
 - You can only create and manage database-level IP firewall rules for master and user databases by using Transact-SQL statements and only after you configure the first server-level firewall.
 - If you specify an IP address range in the database-level IP firewall rule that's outside the range in the server-level IP firewall rule, only those clients that have IP addresses in the database-level range can access the database.
-- You can have a maximum of 128 database-level IP firewall rules for a database. For more information about configuring database-level IP firewall rules, see the example later in this article and see [sp_set_database_firewall_rule (Azure SQL Database)](/sql/relational-databases/system-stored-procedures/sp-set-database-firewall-rule-azure-sql-database).
+- The default value is up to 256 database-level IP firewall rules for a database. For more information about configuring database-level IP firewall rules, see the example later in this article and see [sp_set_database_firewall_rule (Azure SQL Database)](/sql/relational-databases/system-stored-procedures/sp-set-database-firewall-rule-azure-sql-database).
 
 ### Recommendations for how to set firewall rules
 

docs/integration-services/devops/ssis-devops-standalone.md

@@ -73,7 +73,7 @@ SSISBuild.exe -project|-p:<dtproj file path> [-configuration|-c:<configuration n
     SSISBuild.exe -p:C:\projects\demo\demo.dtproj -c:DevConfiguration -pp:encryptionpassword -o:D:\folder
     ```
 
-- Build a dtproj with configuration "DevConfiguration", encrypted with password, striping its sensitive data, and log level DIAG:
+- Build a dtproj with configuration "DevConfiguration", encrypted with password, stripping its sensitive data, and log level DIAG:
     ```
     SSISBuild.exe -p:C:\projects\demo\demo.dtproj -c:DevConfiguration -pp:encryptionpassword -ss -l:diag
     ```

docs/t-sql/functions/json-modify-transact-sql.md

@@ -271,7 +271,7 @@ PRINT @info
     "skills": ["C#", "SQL"]
 } {
     "name": "John",
-    "skills": ["C#", "T-SQL", "Azure"]
+    "skills": "[\"C#\",\"T-SQL\",\"Azure\"]"
 }
 ```  
 

docs/t-sql/statements/copy-into-transact-sql.md

@@ -274,14 +274,19 @@ IDENTITY_INSERT specifies whether the identity value or values in the imported d
 - IDENTITY_INSERT can only be set for one table at a time.
 
 #### *AUTO_CREATE_TABLE = { 'ON' | 'OFF' }*
-*AUTO_CREATE_TABLE* specifies if the table could be automatically created by working alongside with automatic schema discovery.
+
+*AUTO_CREATE_TABLE* specifies if the table could be automatically created by working alongside with automatic schema discovery. It is available only for parquet files.
 
 - ON: Enables automatic table creation. The COPY INTO process will create a new table automatically by discovering the structure of the file to be loaded.
 - OFF: Automatic table creation is not enabled. Default.
 
 >[!NOTE]  
 > The automatic table creation works alongside with automatic schema discovery. The automatic table creation is NOT enabled by default.
 
+Do not load into hash distributed tables from parquet files using COPY INTO with AUTO_CREATE_TABLE = 'ON'.
+
+If parquet files are to be loaded into hash distributed tables using COPY INTO, load it into a round robin staging table followed by INSERT ... SELECT from that table to the target hash distributed table.
+
 ### Permissions  
 
 The user executing the COPY command must have the following permissions: