Hi,

I am using an existing azure SQL database as backend for my windows store application through Azure mobile services with JS backend.

Currently my tables don't have id,__createdAt,__updatedAt,__deleted,__version these columns. So, now I am updating the tables so that so that I can work with offline synchronization. I have successfully added these columns for all tables except one table.

I don't know the exact issue, The table have 700 thousands of records with 2.9gb of table size... I am guessing due to huge number of records and size the query is not updating the table to add these columns.

I tried to and an empty columns it is adding, but when I try to add id with default value as (newid()) same to __createdAt,__deleted etc. same issue.

Can anyone tell me how alter the table which having huge number of records and data in it??

Hi Narendra,

It sounds like you are hitting the limits of the transaction log.  I would either upgrade to Azure SQL Database Update V12, where this limitation has been removed, or create a new table with the correct schema and iteratively insert into the new table from your old table.

Hi Narendra,

It sounds like you are hitting the limits of the transaction log.  I would either upgrade to Azure SQL Database Update V12, where this limitation has been removed, or create a new table with the correct schema and iteratively insert into the new table from your old table.

• Proposed as answer by Jan EngelsbergMicrosoft employee 18 hours 25 minutes ago

Hi Narendra,

It sounds like you are hitting the limits of the transaction log.  I would either upgrade to Azure SQL Database Update V12, where this limitation has been removed, or create a new table with the correct schema and iteratively insert into the new table from your old table.

• Proposed as answer by Jan EngelsbergMicrosoft employee Tuesday, February 03, 2015 5:04 PM

Hi Narendra,

It sounds like you are hitting the limits of the transaction log.  I would either upgrade to Azure SQL Database Update V12, where this limitation has been removed, or create a new table with the correct schema and iteratively insert into the new table from your old table.

• Proposed as answer by Jan EngelsbergMicrosoft employee Tuesday, February 03, 2015 5:04 PM
• Marked as answer by Lydia ZhangMicrosoft contingent staff, Moderator 8 hours 2 minutes ago

Hi Narendra,

It sounds like you are hitting the limits of the transaction log.  I would either upgrade to Azure SQL Database Update V12, where this limitation has been removed, or create a new table with the correct schema and iteratively insert into the new table from your old table.

• Proposed as answer by Jan EngelsbergMicrosoft employee Tuesday, February 03, 2015 5:04 PM
• Marked as answer by Lydia ZhangMicrosoft contingent staff, Moderator Tuesday, February 10, 2015 3:27 AM