SQL CI VSTS Extension 'remote_data_archive_migration_state'

dtv

Hi,

First, I am using the SQL CI VSTS Extension with an Azure v12 database.

Two questions...

1. How do I apply my License Key to this extension so it does not expire after the trial period?
I looked around in the documentation and there was very little information about the VSTS extension at this time.

2. How/when can I expect the recent updates to be applied to this extension?
I know that the DLM Automation Suite 1.3.20.463 was recently updated with the fix from SQL Compare 11.5.0.397, which I have confirmed works when I run SQL Compare by itself. However, I've been looking around to see how I could (if it is even possible) to update the SQL CI VSTS extension. The 'Sync a database package' operation does not appear to be working anymore.

Here is the error I'm receiving in VSTS:
2016-03-08T03:19:32.6026426Z ==============================================================================
2016-03-08T03:19:32.6036404Z Copyright Copyright c 1999 - 2015 Red Gate Software Ltd
2016-03-08T03:19:32.6036404Z Registering data sources
2016-03-08T03:19:32.6046410Z FINISHED WITH ERROR: Updating database
2016-03-08T03:19:32.6056432Z Error: Comparison of 'Scripts.state' and
2016-03-08T03:19:32.6056432Z 'tcp:REMOVED.database.windows.net.backshop' failed: Invalid column name
2016-03-08T03:19:32.6066421Z 'remote_data_archive_migration_state'.
2016-03-08T03:19:32.6076411Z Updating database failed with error: SQLCompare failed with exit code 126: see output above for more information, or for generic information about this exit code, see: http://www.red-gate.com/sqlCI/ExitCodes/SQLCompare
2016-03-08T03:19:32.6076411Z Running SQLCompare failed with error: SQLCompare failed with exit code 126: see output above for more information, or for generic information about this exit code, see: http://www.red-gate.com/sqlCI/ExitCodes/SQLCompare
2016-03-08T03:19:32.6540519Z ##[error]SQL CI exitcode was 32. See console output for details.


Any insights would be great.

Rob C

Hi,

1. The VSTS extension itself doesn't need activating - it's the build server itself which needs licensing.

2. Is this a hosted build server? If so then there's not much that can be done until Microsoft update the version of the Automation Suite that is installed on their servers.

dtv

Robert Clenshaw wrote:

Hi,

1. The VSTS extension itself doesn't need activating - it's the build server itself which needs licensing.

2. Is this a hosted build server? If so then there's not much that can be done until Microsoft update the version of the Automation Suite that is installed on their servers.

Hi Robert,

1. That makes sense. I did mean the build server even though I said it incorrectly.

2. Yes. This is a hosted build server. Sad to hear that though, seems like there's little use for the extension since we cannot provide the license key for it at this time.

Thanks for replying.

Rob C

Just a quick note to say that the VSTS plugin is now updated so the problem should now be fixed.

dtv

Robert Clenshaw wrote:

Just a quick note to say that the VSTS plugin is now updated so the problem should now be fixed.

Ah yes! I see it.

Thanks for the update Robert.