|You will get better ideas if you reply through the forum! There are others who will be able to help better than I.
Kukreja Sonu wrote:Thanks Holmes. As of now we write all the changed data into an XML file at server and upload the same to a centralized location. Then client downloads the xml and executes queries one by one accordingly to update target DB.
But this is a long process:
1. Populating DB at server with change only data
2. Initiate process to prepare XML based on above data.
3. Client downloads the XML and update target DB.
This takes around 3-4 days for single run. So, we want to have some other process if possible to minimize the time
The more I think about this the nastier it gets, are you up to changing the way you identify your change sets or do you have to stick with the current design/structure?
First I would look into change the format from xml to something less verbose. XML is fine for communication as a transport medium it sucks. We use CSV.
It sounds like each client has a different requirement!
Never underestimate the power of human stupidity