Azure, Export Hyperscale Database to BacPac failed due to Vector datatype column in a table.

Hi Micael Uthas

Greetings!!

The issue you're encountering is due to the VECTOR data type in your Hyperscale SQL database, which isn't currently supported by the BacPac export process. BacPac files are designed for schema and data portability, but they don't support newer or specialized types like VECTOR.

For more information, please refer the document:
https://learn.microsoft.com/en-us/azure/azure-sql/database/reverse-migrate-from-hyperscale?view=azuresql&tabs=azure-portal#limitations-for-reverse-migration

The error message suggests: "Change the length of '5' to 'max' on the column"

However, this is likely a misleading part of the message. The real issue is the unsupported data type, not the length.

Workaround:

To successfully export your database to Blob storage as a BacPac, you can:

Temporarily remove or exclude the VECTOR column:

• Create a copy of the Articles table without the embedding column.
• Export the modified database.
• Reintroduce the VECTOR column after import if needed.

Use a script-based export/import:

• Instead of BacPac, use BACPAC alternatives like DACPAC or SQL scripts for schema and data migration. These methods give you more control over what gets exported.

Use Azure Data Factory or custom ETL:

• If you need to preserve the VECTOR data, consider exporting it separately using Azure Data Factory or a custom ETL pipeline.

Hope this helps. Do let us know if you any further queries.

If this answers your query, do click Accept Answer and Yes for was this answer helpful. And, if you have any further query do let us know.