importing DB from another SQL server

[anguo]

Hello,

I need to set up a development platform at home with a copy
of a DB from a SQL server at a friend's company.
So far, all my attempts at backup/restore or export/import
have failed despite my reading all the documentation I
could find (I am a newbie).

Using DTS/Export wizard, I tried to export the DB first to a
plain text file, then to an excells file. After having gone
through all the screens, the export script runs. It
exported all the data for close to one hour, but at the end
I only get a 0kb empty text file, or 5kb empty excells
file.
Is there a feature on SQL server preventing export (such as
for security reasons)? Then why would the export wizard run
for so long, just to output nothing?

Since it's only for developement, I don't need the latest
data yet, so I burned on CD the .bak backup files
previously made, but I couldn't import nor restore them on
the other machine. Depending on what I tried, I had various
error messages, like
* an improper login and password (which should this be: that
of the owner of the DB on the source SQL server, or that of
the SQL admin or windows admin on the target server?),
* an error saying that the backup doesn't belong to the
empty DB I try to restore to...
* I even managed to import a mydbname.bak.dns file with the
DTS wizard (apparently it was a backup of an Access DB, not
the SQL Server DB I need), but the import script runs
apparently smoothly for a while, but then the target DB
didn't contain any of the imported tables, only the sys
tables.

For the last several weeks, I have tried everything I could
think of, read the docs, but still I am at a loss as to how
to import or make a copy on my system of the BD from the
office.

What would be the proper procedure to import/restore the
copies of the backup I have burnt on CD into my fresh
install of W2000/SP1 + SQL Server 2000?
Failing that, I can go back to my friend's office and try
again to export the data, but how do I make sure I don't
end up with an empty file?

thank you,

Anguo.

--

http://www.masquilier.org/
Condorcet, Approval alternative, better voting methods.

http://www.gnosis-usa.com/
Revolutionary Psychology, White Tantrism, Dream Yoga...

http://www.reuniting.info/
Intimate Relationships, peace and harmony in the couple.

[Simon Hayes]

"anguo" <linux-tw-...@masquilier.org> wrote in message
news:cv43hd$30vq$1...@news.giga.net.tw...

Check out this KB article:

http://support.microsoft.com/default.aspx?scid=kb;en-us;314546

The easiest solution would probably be to backup then restore the database -
this is described in the article. You don't need to restore to an existing
database, as you can create a new database when you restore - just give the
new name in the Enterprise Manager restore dialogue box, or see example E
under "RESTORE" in Books Online.

Simon

[anguo]

Simon Hayes wrote:
> Check out this KB article:
>
>
http://support.microsoft.com/default.aspx?scid=kb;en-us;314546
>
> The easiest solution would probably be to backup then
> restore the database - this is described in the article.
> You don't need to restore to an existing
> database, as you can create a new database when you
> restore - just give the new name in the Enterprise Manager
> restore dialogue box, or see example E under "RESTORE" in
> Books Online.
>
> Simon

Thank you Simon,

I am looking into it right now.

[Ken Post]

I've also found that software from Red-Gate.com is very useful once you
get the 2 copies of the database both up. You can make changes to
devel and then apply them to the production server.