Up until 7SP4 we had to copy objects and data between sql server 7 databases, wait for it to blow up
and then use the copy tables option. Then be prepared to rebuild all indices and views.
Oh, if your application uses UD datatypes you'll need to recreate those as well.

SP4 also fixes some AV (access violation) errors. We thought the db was corrupt but it turned out to be an MS bug.

G'LUCK

-----Original Message-----
From: Phil Shuttleworth [mailto:Phil.[Email Address Removed]
Sent: Tuesday, June 18, 2002 5:08 AM
To: Lazydba (E-mail)
Subject: Copying Database

I am attempting to set up a database as a copy of an existing database.

In Enterprise Manager, I firstly clicked onto the existing database and
re-named it thereby setting up the new database as a replica of the existing
one. I then attempted, via the Data Transformation Service in the Tools
menu, to Import Data taking the optiin of 'Transfer objects and data between
SQL Server 7.0 databases'.

After about three minutes running, I got the following message:

"Failed to transfer objects and data between SQL Server 7.0
databases", and although the tables seemed to be there, there was no data
in them.

Does anyone please know the reason for this?

Phil Shuttleworth

DBA, IT Services
University of Central England, BIRMINGHAM B42 2SU, UK
Tel: +44(0)121 331 5664 Fax: +44(0)121 356 2875
E-mail: Phil.[Email Address Removed] unsubscribe, e-mail: mssqldba-[Email Address Removed] additional commands, e-mail: mssqldba-[Email Address Removed]MS Sql Server LazyDBA home page