Unable to deprovision database from non-existent synch group

Question

Hello

I recently rebuilt my Windows 8 development machine. I have previously deleted and created various SQL Azure synch groups. According to Azure portal I currently have no sync groups, yet I do have a SQL Azure database with sync tables.

I installed the current data sync agent, regenerated the agent key and successfully pinged the sync service.

Deprovisioning utility failed "either the database is not provisioned for sync or you do not have permissions to the sync configuration tables."

How do I properly deprovision sync from this SQL Azure database?

---

Jen

Answer 1

Hi Jen,

If the Azure portal shows you have no sync groups, then what do you mean by saying "yet I do have a SQL Azure database with sync tables"? Whenever you delete a sync group, deprovison task will be executed on members of that sync group automatically, you don't need to deprovison it manually after delete sync group.

Answer 2

Jen,

can you query the scope_config table and see if it contains any rows and what does the scope_status column says...

Answer 3

looks the data sync agent lost the connection string of the local database.

Could you first do 'Edit Credential' to reset the connection string on the local db and then deprovision again

Answer 4

I know deleting a sync group should delete sync tables but we've had a number of cases over the last year where a synch group has been deleted yet the sync tables are not removed. We 'manually' deprovision in those cases.

---

Jen

Answer 5

3 rows JuneT. Last column C in each row.

---

Jen

Answer 6

There is no local db. We take a copy from SQL Azure whenever we want to do some development. We want to get rid of the sync tables in the Azure database from a prior sync group so we can get a clean copy.

---

Jen

Answer 7

if it has a status of C, then it means its still tagged as "Provisioned".

is it just the scope_xxx tables that's left or does your database still have the tracking tables, stored procs, etc... created by the service?

if its just the tables, just drop them.

Answer 8

The whole schema is still there JuneT ... tables, triggers ... everything you would normally expect if it were provisioned for sync.

---

Jen

hundreds of objects; not really viable to drop them all manually.

Answer 9

does the scope_info_dss table exist in your database?

Answer 10

There is no scope_info_dss table  Renhe Li

---

Jen

Answer 11

try provisioning a dummy sync group, even with just one table so it recreates the scope_info table.

then delete the sync group and run the deprovisioning utility again.

Answer 12

That did the trick JuneT. Thank you.

---

Jen