We currently have a production database and a development database and
periodically I will have to fix some data. Currently I will make a backup
of the production DB and copy that to the Dev server and then restore that
copy of the DB. The DB is several Gigs and so the copy takes a while and
the restore takes a while too. Is there a better or faster way to move the
data from the production server to the development server?
Best regards,
Sean GahanYou might be able to eliminate the copy step. One way is to backup to
the target system, the other is to restore from the backup file while
it is on the source system. In either case the copy of SQL Server
moving the data over the network has to be running under an account
that has the proper rights to the other server, and will need to use a
UNC path of the form \\servername\sharename\folder\subfolder\file.ext
rather than a mapped drive letter.
Roy Harvey
Beacon Falls, CT
On Tue, 2 Jan 2007 10:42:22 -0800, "Sean Gahan" <SeanGahan> wrote:
>We currently have a production database and a development database and
>periodically I will have to fix some data. Currently I will make a backup
>of the production DB and copy that to the Dev server and then restore that
>copy of the DB. The DB is several Gigs and so the copy takes a while and
>the restore takes a while too. Is there a better or faster way to move the
>data from the production server to the development server?
>Best regards,
>Sean Gahan
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment