importing DB from another SQL server

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.gnosis-usa.com/
Revolutionary Psychology, White Tantrism, Dream Yoga...
http://www.reuniting.info/
Intimate Relationships, peace and harmony in the couple.
Message posted via http://www.droptable.comIf you do not need the data, why not just script the objects out and run it
against your new server. You can use Enterprise Manager/QueryAnalyser to
script the DDL. You can also use QALite from rac4sql.net for this.
-oj
"Anguo via droptable.com" <forum@.droptable.com> wrote in message
news:86f3fb22900e440bbd05d784d291fc06@.SQ
droptable.com...
> 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.gnosis-usa.com/
> Revolutionary Psychology, White Tantrism, Dream Yoga...
> http://www.reuniting.info/
> Intimate Relationships, peace and harmony in the couple.
> --
> Message posted via http://www.droptable.com|||Thanks, but I do need some data even if it is not up to date, in order to
work with as a sample.
I have been advised to read this article:
HOW TO: Move Databases Between Computers That Are Running SQL Server
http://support.microsoft.com/defaul...;en-us;314546#9
I am looking into it.
I still would like to know how come the export procedure didn't work and I
only got an empty file.
Thank you.
Message posted via http://www.droptable.com|||> I still would like to know how come the export procedure didn't work and I
> only got an empty file.
I suggest you post that question to the DTS group. There are many many possi
bilities within DTS, and
you would need to give us information on exactly how you specified the DTS e
xecution.
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
"Anguo via droptable.com" <forum@.droptable.com> wrote in message
news:3298983102dd4e1db62952dfbea8e130@.SQ
droptable.com...
> Thanks, but I do need some data even if it is not up to date, in order to
> work with as a sample.
>
> I have been advised to read this article:
> HOW TO: Move Databases Between Computers That Are Running SQL Server
> http://support.microsoft.com/defaul...;en-us;314546#9
> I am looking into it.
> I still would like to know how come the export procedure didn't work and I
> only got an empty file.
> Thank you.
> --
> Message posted via http://www.droptable.com|||The best (most reliable, fastest and fewest steps involved) method to
restore a DB on other server is to detach the production MDFs, make a copy
of the MDF files, re-attach the production MDFs, then reattach the MDFs on
your development PC. You don't have to worry about data type conversion,
scripting SPs, re-importing RI data in proper order, etc.
If you want to use DTS, then keep in ming the following. When exporting
to text, you may encounter data type conversion issues. Also, the problem
with Excel is that it supports only 60k rows, and perhaps that is the
problem you are currently having. The best externals file format for DTSing
into is MS Access. It preserves the data types and can contain all the
tables in a single Access database file. Regardless of the export format you
choose, the SPs, Views, etc. need to be scripted sperately.
"Anguo via droptable.com" <forum@.droptable.com> wrote in message
news:86f3fb22900e440bbd05d784d291fc06@.SQ
droptable.com...
> 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.gnosis-usa.com/
> Revolutionary Psychology, White Tantrism, Dream Yoga...
> http://www.reuniting.info/
> Intimate Relationships, peace and harmony in the couple.
> --
> Message posted via http://www.droptable.com