If your table survives these limitations and you have enabled it for stretching, you should be aware of these additional constraints:

• Uniqueness is not enforced for UNIQUE constraints and PRIMARY KEY constraints in the Azure table that contains the migrated data.
• You cannot UPDATE or DELETE rows that have been migrated or rows that are eligible for migration in a Stretch-enabled table or in a view that includes Stretch-enabled tables.
• You cannot INSERT rows into a Stretch-enabled table on a linked server.
• You cannot create an index for a view that includes Stretch-enabled tables.
• Filters on SQL Server indexes are not propagated to the remote table.

These limitations are not unexpected; the Azure portion of data is automatically managed and it should be protected from direct access and changes. Therefore, these limitations are acceptable, especially compared to all those listed in the previous sections.