Our dev team have reported a missing index from a restored DB.
i have tested this by performing a restore from Azure to Azure
and a restore for SQL/FTP to Azure.
the restore from Azure to Azure has 3 indexes for a specific table
the SQL/FTP restore only has 2
the missing index is an issue.
there is nothing in the logs to suggest either the back up or the restore had any issues.
Regards
Colin.
Any chance of an update on this ?
Hello Colin,
Thank you for your message. Could you please contact our support team at support@sqlbackupandftp.com so we can assist you further?
i only posted this 2 weeks ago.
and the best reply too email support.
it’s just time wasting.
Dear Colin,
We sincerely apologize for the inconvenience and appreciate your cooperation in helping us analyze this issue.
The same behavior also occurs when using SSMS (Export/Import Data-tier Application). This is caused by the way Azure SQL Database processes Data-tier Application exports and imports — in some cases, certain index definitions may not be included.
Unfortunately, since this mechanism is fully managed by Microsoft Azure SQL, this behavior is outside of our control.
As an alternative, we recommend trying the Microsoft SQL Server (SQL dump) connection type in your connection settings. This method connects to your Azure SQL Database as a remote SQL Server instance, using a different backup and restore mechanism that might help bypass the Data-tier Application limitation.
We’ll continue to monitor this behavior and share any updates if Microsoft modifies how DAC export/import handles indexes in future releases.
Thank you for your understanding.
