Even if your table does not violate constraints from the preceding table of limitations, it is still far away from fulfilling the conditions for stretching. The following properties and characteristics of table columns don't support the Stretch DB feature:

• Unsupported data types: Deprecated large data types (text, ntext, and image), XML, timestamp, sql_variant, spatial data types (geometry and geography), hierarchyId, user-defined CLR data types
• Computed columns
• Default constraints
• Check constraints

Let's repeat a similar analysis of the reduced potential of Stretch DB for the items from this list. I think that Microsoft has a balanced approach with deprecated data types; they are not removed in order to prevent the breaking of changes in legacy code, but all new features don't support them. This is completely correct and it should not be considered a limitation.

The other unsupported data types are used rarely and do not represent a huge limitation.

However, the most important limitation in this list is that a table column in a Stretch Database cannot have a default or check constraint. This is a huge limitation and significantly reduces the usage and importance of the Stretch DB feature!

Also, as mentioned before, you should not remove database objects created to implement database integrity just to enable Stretch DB. Default constraints and foreign keys are the reasons why there is not a single table in the AdventureWorks2014 database that is ready for stretching.