I have a unique situation that I am hoping will start a conversation in this forum. We have an old app that was written using SQL Anywhere (syabase smaller version) on the dbms side. We have now taken that sql anywhere db and converted it to sql server and our app is able to connect to it and works great. We are now planning to change our client app and rewrite it in more current tool like .net or something against the sql server db we converted from sql anywhere. The problem is that sql anywhere db we converted was created so poorly that creating a brand new app against that poor schema will cause problems in future (major problems becasue this schema basically sucks to put it mildly). We can clean up the schema and create a new database on sql server based on this new schema, the challenge is that now we have to have our current app run against the old db and be in production all along while we develop new app against the new db, once we are done we will just flip the switch and start using the new app against new db but how do we keep the data in sync between these two dbs while we are developing the new app that could take a long time. Besides keeping things in sync also keep in mind that both dbs will have diffrent schemas. We have thought about having triggers on the old db that will have logic to update the new db but that will slow things down and we will have to write tons of triggers, is there anyother way sql server can do this? Sorry for the long question.