|
Home > Archive > MS SQL Data Warehousing > July 2005 > Re: Can I pick your brains for a second? transferring a large database problem.
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
Re: Can I pick your brains for a second? transferring a large database problem.
|
|
| Peter Nolan 2005-06-21, 11:23 am |
| Hi Scott,
maybe I'm not 'with it' but why do you want to move 30GB of data
between machines just to keep 2 databases in sync?
Do you mean you have two databases being updated and that you then need
BOTH databases to be the same after the syncing process?
Or do you mean you have one database being updated and you need to get
the updates for that one across to the other?
If the second one, and you have absolutely no way to get the changes
from the database you can always do delta file generation.....that is,
dump the tables and compare today vs yesterday, detect the changes and
then send the delta file to the second machine....only a small number
of rows are likely to have changes unless someone is updating lots of
rows for no good reason....I have publised free tools to do this sort
of thing on windows as files to get far better performance than doing
it at a database level.....write to me at peter@peternolan.com if you
want to try them......
Best Regards
Peter
| |
| Scott M 2005-07-07, 8:23 pm |
| It's a huge database that is recreated from our billing software. The
"main" database is housed in a different city and we have a database here
for performance reasons.
"Peter Nolan" <peter@peternolan.com> wrote in message
news:1119366628.053264.191240@z14g2000cwz.googlegroups.com...
> Hi Scott,
> maybe I'm not 'with it' but why do you want to move 30GB of data
> between machines just to keep 2 databases in sync?
>
> Do you mean you have two databases being updated and that you then need
> BOTH databases to be the same after the syncing process?
>
> Or do you mean you have one database being updated and you need to get
> the updates for that one across to the other?
>
> If the second one, and you have absolutely no way to get the changes
> from the database you can always do delta file generation.....that is,
> dump the tables and compare today vs yesterday, detect the changes and
> then send the delta file to the second machine....only a small number
> of rows are likely to have changes unless someone is updating lots of
> rows for no good reason....I have publised free tools to do this sort
> of thing on windows as files to get far better performance than doing
> it at a database level.....write to me at peter@peternolan.com if you
> want to try them......
>
> Best Regards
>
> Peter
>
|
|
|
|
|