"SP" <SP@discussions.microsoft.com> wrote in message
news:94FCA706-659C-483A-BFED-25EDC4BEC561@microsoft.com...
> Can you run DBCC Check DB and See if something going wierd also run DBcc
> repair to fix it fast before doing any importing.
>
> "Peter Croft" wrote:
>
> > We run an ASP website with an MS SQL Server database on a third party
> > server.
> > Last night it was hacked and data in one table, called Entry, was
changed.
> > I exported the database to my local server (as local1) and corrected the
> > data changes.
> > I then tried to import it back to the remote server and that failed - it
> > didn't transfer the Entry table for some reason and then complained that
it
> > couldn't find it.
> >
> > After much trial and error I set up a new empty database (s2) on the
remote
> > server, and created a new one locally (called new1) with new dummy data
of
> > approx the same size. I was then able to import new1 into s2
successfully.
> > I then tried importing the old database local1 into the new server s2
and
> > that failed as before. I then tried to re-import new1 into s2 and that
> > failed this time although it was fine before.
> > So it seems that the old database is somehow "corrupting" the new one.
> > Can someone please suggest what might be happening and how I get round
this?
> > I find the log files not much help and am very keen to get our system
back
> > live.
> > Thanks in advance,
> > Peter Croft
> >
> >
> >
> >