is this db2 on os390 or AS400 or UDB on win/unix/..

you've already been advised to use sp_attach_db ... (see bol)

Then perform the checkdb

Any backup-files ??? (full / diff / log)

All ddl scripted nicely ?

Review you backup-schema !

oh please stay with CODD' s rules !

http://www.sqlservercentral.com/columnists/fkalis/coddsrules.asp

Basics of any RDBMS :

- know your relationships.

- use meaningless keys. It makes schema-knowlage mandatory ! and will avoid symantic errors !

-...

the rough way :

- Select  'exec sp_refreshview @viewname = ''' + u.name + '.'+ o.name + ''' ' + char(13) + ' go '

from  sysobjects o

inner join sysusers u...

http://www.sqlservercentral.com/columnists/sjones/performancemonitoringbasiccounters.asp

will put you on track.

- There are # of articles/forumthreads concerning performance monitoring.

this is also very usefull :

http://www.sql-server-performance.com/performance_monitor_tips.asp

create tabel mytable(

mybunch_of_columns ....

, tsInserted datetime not null default getdate()

, UserInserted varchar(50) not null default suser_sname()

) ...

This makes you don't have to change your insert-script because if the columns are not mentioned...

With Query Analyzer or EM : sp_detatch_db 'yourUserdb'

With explorer move the file to the correct location.

With Query Analyzer or EM : sp_attach_db 'yourUserdb', 'FileLocationAndName.MDF', 'FileLocationAndName.Ldf'

For system databases check http://support.microsoft.com/default.aspx?scid=kb%3ben-us%3b224071

Maybe even...

Antares686 sead it all

- Figure out the average actual datalength of you char columns.

     SELECT avg(datalength(...

- how many rows get into a single datapage ?

- you could rebuild the clustering indexes.

log on to the server using your sqlagent account and then try to run the package from EM\edit dts package.

You'll get more detailed errorinfo.

Great to know I'm not the only one that has those concerns

"...size of the log file and truncates & shrinks it ..."

I hope your DRP can cope with that

We don't use fixed- or max-memory setting on most of our sql2k-servers. Only when experiencing  sql-paging, it occurs we put a max-memory on it.

I believe the recomendation to leave 512Mb is...

that's what I assumed.

Normaly, just the statistics will not cause such log-load.

dbreindex rewrites it all. this log-overhead can be reduced by switching to bulk-logged recovery mode.

switch to bluk-logging before performing your maintenance !

full-logged it logs everything !