Hi,
I've used SQL Enterprise Manager to Export my selected db's locally.
My main question is how do I move the export to another pc - which
files need to be moved, etc?

Thanks
Louis

Hi Louis,

How did you exactly export you databases?

Normally the easiest way to move databases is to backup, move the backup
file to the new PC, and then restore.

You could also use detach, copy the MDF and LDF files, then attach on the
new PC (but you have to attach back to the original PC too, if you need the
databases there). Not worth the trouble unless you do not have space to save
a backup file.

Alternatively you can script your database objects and export the data, then
apply the scripts to the new PC and import the data. This is manual approach
that is not needed unless you want to change structure for some objects
during the transfer, filter data, etc.

HTH,

Plamen Ratchev
http://www.SQLStudio.com

On Dec 14, 1:05 pm, "Plamen Ratchev" <Pla... (AT) SQLStudio (DOT) com> wrote:

Hi Plamen,

Thanks for your reply.

I created a new local db and imported the tables from the live
database, selecting "copy objects and data between SQL Server
databases", then left "copy all objects" and "use default options"
selected on the next step, then I selected "run immediately" but
didn't save the DTS package.
Do I need to take the live db offline in order to do this (I get a
failure message halfway through the import process).

Thanks,
Louis

On Dec 14, 1:05 pm, "Plamen Ratchev" <Pla... (AT) SQLStudio (DOT) com> wrote:
Hi Plamen,
Thanks for your email.
I've created a new local db and imported the tables from the live db.
This will fail when I choose to 'copy objects and data between SQL
Server databases' and then leave 'copy all objects' and 'use default
objects' and 'run immediately' in the next step, leaving 'save DTS'
unchecked. Would I need to take the live db offline before copying?
Thanks
Louis

You could get different errors when using the Import/Export wizard to copy a
database. No, you do not need to have the live database off-line while doing
that.

Instead of using this method I would suggest to use backup and then restore
the backup file. It is easier and a lot more reliable.

Here is a good article that outlines the different approaches to move data
between SQL Server instances:
http://support.microsoft.com/kb/314546

See also the sections in the article that refer to transferring logins and
resolving orphaned users.

HTH,

Plamen Ratchev
http://www.SQLStudio.com