We have 10 databases that get nightly calculations done on them. The routine that does it is a vb.net application that reads data from 8 large tables. It then does a lot of number crunching and writes the results back into 6 additional tables. It creates about 100k records per database per night (each night replaces the previous night's numbers).<br /><br />Currently the routine takes 12+ hours to run, I have tried running multiple copies of my app which tends to only cause SQL to max out the processors on the SQL server which seems to make the whole process take longer.<br /><br />The better long term solution would be to change the way the nightly routines work so that we're not doing as much work, and therefore, it doesn't take as long or work the server as hard (suggestions welcome [<img src='/community/emoticons/emotion-1.gif' alt='' />] ) however, I need a quick fix because this is a production system.<br /><br />Since this basically runs on a snapshot of the data as of close of business (few or no users are online in the evenings.) Would it be possible (or a good idea) to copy the data to another server (or servers) and run the routines there, and then copy the results back to the main server? Would replication be the way to do this or is there a better way?<br /><br />I'm struggling with the best way to solve this problem quickly. Any suggestions are welcome.