After ftp transfer, database allways corrupted

Hi,
we use ftp to transfer database from one server to another
(detach, ftp copy, attach). Database is pretty large
(~300GB), and when we reattach database files to
destination server, database comes up with errors
(detected by dbcc checkalloc, there is nothing in error
log). We're unable to repair the database, and even if we
use dts to recreate corrupted tables, other tables come up
corrupted...
We use ftp because of the speed... Does anybody know why
is this happening? Any other idea for data transfer?
Thanks,
OJHow often are you doing this? Have you considered doing a backup at one
site, restoring at the other, and then using log shipping/replication to
keep them in sync perpetually?
--
http://www.aspfaq.com/
(Reverse address to reply.)
"OJ" <anonymous@.discussions.microsoft.com> wrote in message
news:018301c495d2$e21fc460$a401280a@.phx.gbl...
> Hi,
> we use ftp to transfer database from one server to another
> (detach, ftp copy, attach). Database is pretty large
> (~300GB), and when we reattach database files to
> destination server, database comes up with errors
> (detected by dbcc checkalloc, there is nothing in error
> log). We're unable to repair the database, and even if we
> use dts to recreate corrupted tables, other tables come up
> corrupted...
> We use ftp because of the speed... Does anybody know why
> is this happening? Any other idea for data transfer?
> Thanks,
> OJ|||Have you run CHECKDB on the original db to make sure it isn't corrupted to
begin with?
--
Andrew J. Kelly SQL MVP
"OJ" <anonymous@.discussions.microsoft.com> wrote in message
news:018301c495d2$e21fc460$a401280a@.phx.gbl...
> Hi,
> we use ftp to transfer database from one server to another
> (detach, ftp copy, attach). Database is pretty large
> (~300GB), and when we reattach database files to
> destination server, database comes up with errors
> (detected by dbcc checkalloc, there is nothing in error
> log). We're unable to repair the database, and even if we
> use dts to recreate corrupted tables, other tables come up
> corrupted...
> We use ftp because of the speed... Does anybody know why
> is this happening? Any other idea for data transfer?
> Thanks,
> OJ|||No, because we build this database on the staging server
monthly and after transfer to destination server set it to
read only mode...
Thanks
>--Original Message--
>How often are you doing this? Have you considered doing
a backup at one
>site, restoring at the other, and then using log
shipping/replication to
>keep them in sync perpetually?
>--
>http://www.aspfaq.com/
>(Reverse address to reply.)
>
>
>"OJ" <anonymous@.discussions.microsoft.com> wrote in
message
>news:018301c495d2$e21fc460$a401280a@.phx.gbl...
>> Hi,
>> we use ftp to transfer database from one server to
another
>> (detach, ftp copy, attach). Database is pretty large
>> (~300GB), and when we reattach database files to
>> destination server, database comes up with errors
>> (detected by dbcc checkalloc, there is nothing in error
>> log). We're unable to repair the database, and even if
we
>> use dts to recreate corrupted tables, other tables come
up
>> corrupted...
>> We use ftp because of the speed... Does anybody know why
>> is this happening? Any other idea for data transfer?
>> Thanks,
>> OJ
>
>.
>|||Yes we have.We have every day daily maintenance job which
checks database integrity...
>--Original Message--
>Have you run CHECKDB on the original db to make sure it
isn't corrupted to
>begin with?
>--
>Andrew J. Kelly SQL MVP
>
>"OJ" <anonymous@.discussions.microsoft.com> wrote in
message
>news:018301c495d2$e21fc460$a401280a@.phx.gbl...
>> Hi,
>> we use ftp to transfer database from one server to
another
>> (detach, ftp copy, attach). Database is pretty large
>> (~300GB), and when we reattach database files to
>> destination server, database comes up with errors
>> (detected by dbcc checkalloc, there is nothing in error
>> log). We're unable to repair the database, and even if
we
>> use dts to recreate corrupted tables, other tables come
up
>> corrupted...
>> We use ftp because of the speed... Does anybody know why
>> is this happening? Any other idea for data transfer?
>> Thanks,
>> OJ
>
>.
>|||I would suspect the FTP process it self then. I have had issues in the past
with large FTP files getting corrupted especially if it is not sent in
binary format. You might want to look at using a product such as SQL
LiteSpeed to provide you with a compressed backup that you can then FTP.
Your likely to get a file that is up to 70 or 80% smaller than the detached
one you are using now.
--
Andrew J. Kelly SQL MVP
"OJ" <anonymous@.discussions.microsoft.com> wrote in message
news:030201c495e6$517ab730$a401280a@.phx.gbl...
> Yes we have.We have every day daily maintenance job which
> checks database integrity...
> >--Original Message--
> >Have you run CHECKDB on the original db to make sure it
> isn't corrupted to
> >begin with?
> >
> >--
> >Andrew J. Kelly SQL MVP
> >
> >
> >"OJ" <anonymous@.discussions.microsoft.com> wrote in
> message
> >news:018301c495d2$e21fc460$a401280a@.phx.gbl...
> >> Hi,
> >> we use ftp to transfer database from one server to
> another
> >> (detach, ftp copy, attach). Database is pretty large
> >> (~300GB), and when we reattach database files to
> >> destination server, database comes up with errors
> >> (detected by dbcc checkalloc, there is nothing in error
> >> log). We're unable to repair the database, and even if
> we
> >> use dts to recreate corrupted tables, other tables come
> up
> >> corrupted...
> >> We use ftp because of the speed... Does anybody know why
> >> is this happening? Any other idea for data transfer?
> >> Thanks,
> >> OJ
> >
> >
> >.
> >