I'm just trially a new ISP And am trying to transfer my
application (VB / Web classes SQL Server) to the new
server.

The old system uses W2K server and SQL Server 2000.

The new System uses W2003 Server Web Edition with MSDE
2000(as pre-loaded).

I've backed up the database (under 100MB) on the original
machine and copied it up and tried to restore it. I get
an error reporting a 'torn page' (and it refuses to show
any content - like the tables).

However, if I take the same backup and restore it on a
development machine (W2003 Server Standard Edition with
SQL Server 2000, it restores fine.

if I run DBCC CHECKDB WITH PHYSICAL_ONLY on the original
database it finds no errors.

I'm currently running a chkdsk on the new machine, but
don't expect that to show anything unexpected.

Hope some one has some idea on this!


Iain

Strange... Does it come clean if you do a CHECKDB without PHYSICAL_ONLY?

Yes.

My CHKDSK is done and seems to have found no problems.

I've uploaded 2 different backups of the database (one
from monday and one from today), both report a torn page.

I've also tried to restore this into another database
(XXX2) to avoid using the same file area and this failed
in the same way.

Although the DB I've restored locally shows no errors at
all, the remote one shows dozens of (largely
incomprehensible!) errors.

I suppose the next thing to see if the file has been
corrupted in transit - but all I'm doing is using ftp!

Iain

>-----Original Message-----
>Strange... Does it come clean if you do a CHECKDB
without PHYSICAL_ONLY?
[..]

You don't have any type of compression turned on, do you?

Not to my knowledge.

Now what I've done is to ftp from the original machine to
the new one and re-restored. It worked.

The implication is that the ftp from my local machine to
the ISP server corrupted the (2!) backups whereas the ftp
into the local machine or the ISP server (from the source
machine) did not.

This makes no kind of sense to me at all. The only thing
that I can imagine is that IE thought XXX.BAk (on
sending) was an ASCII file, but if it had done CRLF
processing, I would not have expected the damn thing to
have loaded at all!

Confused?

Sure as hell am.

Iain

(BUt it's going, now - thanks for your suggestions!)
[..]

It may be obvious but you have set FTP into binary transfer before copying the file?

Mike John

"Iain" <anonymous> wrote in message news:280a
[..]

Being Lazy, I trusted that IE would know what to do.

In truth it GETs the file in binary mode fine (from 2
machines), but it seems to PUT it in ASCII.

Wierd.

Iain
>-----Original Message-----
>It may be obvious but you have set FTP into binary
transfer before copying the file?
>
>Mike John
>
>"Iain" <anonymous> wrote in
message news:280a
[..]