Comments
Sort by recent activity
Okay -- it's not a bug or a feature. It was user error, I think.
Having never seen the SQL Compare user interface before, I had been clicking around here and there to familiarize myself with the product. Somehow -- and this is the strange part -- I thought I had only one table checked for synchronization when in fact all User objects were checked. Because there were users in the remote DB (added by my web host) that did not exist in my local DB, SQL Compare dropped them.
I have since used the Filter feature to exclude and hide User objects so that this cannot happen I again.
As a happy ending, I used SQL Compare to synchronize all of my local asp_net tables and views with the remote versions (they differed in auto-generated contraint names) and it worked perfectly. / comments
Okay -- it's not a bug or a feature. It was user error, I think.
Having never seen the SQL Compare user interface before, I had been clicking around here and there to familiarize myself with the p...