Tag Info

New answers tagged

0

First: synchronize 1 table from Azure to Sql Server. Second: Execute some Store procedures in the SQL Server 2005 instance. And third: Synchronize various tables from Sql Server to Azure sequentially. You can use the Azure data sync, but its buggy - since I never managed to get it running flawlessly for even a week. It is still in Preview mode with ...


0

The blog post you have essentially says that GUIDs are OK for SQL Database, due to the fact that Microsoft will compensate for the fragmentation and performance issues for you. I can't say that I've seen this work well for anyone, but if you truly need to create unique identifiers for portability, then GUIDs are one way to go. You can also read this post ...


0

You can just make an extra index on the GUID column, in addition to what you internally use as a primary key index. Guid would come in most handy if storing a record ID client side. This gives a lesser chance of someone spoofing user IDs that are sequentially or incremental and obvious to predict.



Top 50 recent answers are included