Export fails copying dbase from 1 server two another

HI I tried the export wizard mssql2000 and for several dbases it works for
most but for 1 dbase it stops after creating all the tables and just says
that it fails. I noticed that it only copies over a few of the views so not
sure if this is were the problem is. I am planning on trying to do a dbase
backup on the source machine and then copying the file to the destination
machine and doing a restore to see if this works. Any ideas?
--
Paul G
Software engineer.This kind of stuff happens. Here is onle likely scenario:
You have views/procs/functions/etc that are no longer valid in your source
database. This happens by schema changes and the dependent objects hav
become obsolete, but still exist. Now when you script them out and try to
run them on the new server (which is what the export wizard is doing), you
get errors. For example, the table or a column referenced in a view no
longer exists ... crash.
Make sure to clean up your source DB and see if that helps.
HTH,
John Scragg
"Paul" wrote:

> HI I tried the export wizard mssql2000 and for several dbases it works for
> most but for 1 dbase it stops after creating all the tables and just says
> that it fails. I noticed that it only copies over a few of the views so n
ot
> sure if this is were the problem is. I am planning on trying to do a dbas
e
> backup on the source machine and then copying the file to the destination
> machine and doing a restore to see if this works. Any ideas?
> --
> Paul G
> Software engineer.|||ok thanks for the information, nice to know what is causing the problem. Th
e
database that failed has been around for a long time so probably does need t
o
be cleaned up as stated.
--
Paul G
Software engineer.
"John Scragg" wrote:
[vbcol=seagreen]
> This kind of stuff happens. Here is onle likely scenario:
> You have views/procs/functions/etc that are no longer valid in your source
> database. This happens by schema changes and the dependent objects hav
> become obsolete, but still exist. Now when you script them out and try to
> run them on the new server (which is what the export wizard is doing), you
> get errors. For example, the table or a column referenced in a view no
> longer exists ... crash.
> Make sure to clean up your source DB and see if that helps.
> HTH,
> John Scragg
> "Paul" wrote:
>sql