Backup and restore Azure database

Apr 2, 2014 at 11:34 PM
I am attempting to copy the magelia database from one azure server to another. There are two ways of doing this generically for azure databases, the first it creating a bacpac file from within the azure administration console and the other is using sql server management studio (there may be more ways I don't know of.) However, both ways fail for the magelia database and the errors look very similar:

Error SQL71501: Trigger: [magelia_dataBurst-8c94c04d79c3c80af5f9000ff076301b-slc|bcba37e874f8ff628de91107acea2cbbefc555b3].[TR_magelia_dataBurst-tmp-8c94c04d79c3c80af5f9000ff076301b-slc|bcba37e874f8ff628de91107acea2cbbefc555b3-AttributeValues] contains an unresolved reference to an object. Either the object does not exist or the reference is ambiguous because it could refer to any of the following objects: [magelia_dataBurst-8c94c04d79c3c80af5f9000ff076301b-slc|bcba37e874f8ff628de91107acea2cbbefc555b3].[AttributeValues].[magelia_dataBurst-tmp-8c94c04d79c3c80af5f9000ff076301b-slc|bcba37e874f8ff628de91107acea2cbbefc555b3], [magelia_dataBurst-tmp-8c94c04d79c3c80af5f9000ff076301b-slc|bcba37e874f8ff628de91107acea2cbbefc555b3].[AttributeValues].[AttributeValueId] or [magelia_dataBurst-tmp-8c94c04d79c3c80af5f9000ff076301b-slc|bcba37e874f8ff628de91107acea2cbbefc555b3].[AttributeValues].[magelia_dataBurst-tmp-8c94c04d79c3c80af5f9000ff076301b-slc|bcba37e874f8ff628de91107acea2cbbefc555b3].

I am concerned about this as it is essential that we have a recovery strategy for if there is a catastrophic failure. It seems that the problem is related to the databurst data structures (with some kind of trigger.)
Is there a better way of backing up and restoring data? Thanks in advance,

Apr 3, 2014 at 7:14 PM
Hi Rohan,

Thanks for the issue. Cyril, who leads the R&D at Magelia, investigated the problem.
He reproduced and fixed it in the version 3.0 pre-release that we are about to release (couple of weeks from now).
Depending on your project status, you can either want to wait for the v3 release or contact us to get a pre-release.
That was a good point and we are happy that it is fixed for the next release.