MS Azure SQL DB partitioned table and PK index DDL show up incorrectly in table Script tab (4344794)

MS Azure SQL DB partitioned table and PK index DDL show up incorrectly in table Script tab

In Azure SQL DB, a partitioned table with a partitioned PK index shows the correct DDL in SSMS (SQL Server Management Studio), but incorrect DDL in Toad Data Point (currently using v5.6). Specifically, the partitioning scheme info is not shown, and the ALLOW_ROW_LOCKS and ALLOW_PAGE_LOCKS have incorrect values (they say OFF, which is not the default, whereas they should say ON). The impact of this issue is that the DDL pulled from Toad produces the incorrect result. It will create a non-partitioned table, and will not have the appropriate row/page lock settings. See attached document for details.

"In Toad Data Point, when looking at an Azure SQL DB table that is partitioned, in the Database Explorer tool, "Partitions" tab, it says Partitioned = False.  I.e., it is saying that the table is not partitioned, when in reality it is partitioned. 

WORKAROUND

NONE

 

STATUS

 

Waiting for fix in a future release of Toad Data Point.

QAT-17032