are the SQLagent jobs failing? please post sp_help for this table.

Anyone connected to fdatabase when job tries to restore?

on your destination server in msdb, check out table log_shipping_plan_history, this will have a row for each copy and restore event, this should have info on what happened.

I would remove that backup log statement and the shrink database. Set up a maintenance plan to backup your transaction logs. Frequency of log backups will depend on how much...

r u using log shipping set up by the wizard in SQL 2000 enterprise edition, or some other log shipping set-up?

I would recommend sp_revokedbaccess rather sp_dropuser

don't worry you can't screw anything up. It is as simple as changing option in drop down menu and selecting ok.

TSQL to do the same is 'alter database dbanme set...

not sure which flavour of log shipping you are running, but any errors detailed in the history table in msdb for log shipping?

In enterprise manager, right click on database , select properties, select options tab, it lists the recovery mode in there.

or TSQL command sp_helpdb dbname gives details on database including recovery...

I would say you need to use the 'with move' option when restoring the database to move the database files to drives that are in the dependancies list of the...

along the lines of steves comment that 'the tools we use should be ergonomic, but not simplistic' I have always felt that the important thing is that tools should be...

TRacy.

the difference is

if sysadmin or the database dbo, any objects you create are automatically owned by dbo, if only in the db_owner group they will be owned by the user...

cscott, how goes it , is it fixed, please post resolution if it is for those that come along later.

just a thought, what version of SQL 2000 are you migrating...

they will need server role securityadmin as well to create the logins.

If they all login as part of the same windows group they will own the databases they create and...

have you tried just splatting over it with a restore database................with replace

Christopher, r u still happy these messages are still not causing you a problem. I get the exact same messages after log restores due to log shipping, trouble is there...