Home All Groups Group Topic Archive Search About
Author
16 Dec 2005 1:45 PM
jkane
I need to copy a significant amount of data (1-2gb)  during work hours
to another database for some lengthy numeric calculations and a report.
Phantom rows inserted during the copy operation would be a problem but
a serializable transaction would impact availability.  I was
considering using BCP to export the data with a query since I think it
would be faster than directly copying across databases with t-sql.  The
BCP docs dont say anything about other users inserting during a bulk
export.  Are inserts prevented during bulk export?  Is BCP a good way
to go? Other options?  I must support sql2k and cannot rely on new 2005
features.

Jim Kane

Author
16 Dec 2005 2:32 PM
JT
You could restore or re-attach a backup of the production database.

<jk***@satx.rr.com> wrote in message
Show quote
news:1134740711.836936.47380@g47g2000cwa.googlegroups.com...
>I need to copy a significant amount of data (1-2gb)  during work hours
> to another database for some lengthy numeric calculations and a report.
> Phantom rows inserted during the copy operation would be a problem but
> a serializable transaction would impact availability.  I was
> considering using BCP to export the data with a query since I think it
> would be faster than directly copying across databases with t-sql.  The
> BCP docs dont say anything about other users inserting during a bulk
> export.  Are inserts prevented during bulk export?  Is BCP a good way
> to go? Other options?  I must support sql2k and cannot rely on new 2005
> features.
>
> Jim Kane
>

AddThis Social Bookmark Button