If the current log files are not getting deleted, try re-creating the maintenance plan.

You can also do the following. Substitue your column name instead of id.

select id from tablea where id not in(select id from tableb union select id from tablec union select...

You can also try rebuilding the master with rebuildm utility if you don't want to re-install SQL. This will replace step 3-4 suggested by old hand. You still need to follow...

Can you try starting sql Server through command line i.e. using sqlservr application and see if you get any errors ? Below are the list of parametes

sqlservr [-sinstance_name] [-c] [-dmaster_path] [-f]...

SQL Server has a very robust Backup and recovery strategy which access does not have. (Access does not support tran log backups. )Also, the security model for SQL Server is very...

MSDB only stores information regarding your jobs, DTS packages and maintenance plans. None of your users should be affected directly with you running a checkdb against msdb.

When you open the properties for the maintenance plan by right clicking it, the last tab under it is for reporting. Can you check how many maximum rows are you...

When you backup and restore a user database, the userid's get moved over and not logins. Please make sure that you don't confuse yourself between users and logins. Users are local to...

ftdisk error with eventid 50 indicates that you are having some kind of issues (network issues) while writing data to disk. You might want to investigate into this.

Stander,

If you want to map an id to dbo, execute sp_changedbowner 'domain\user'. You can also mention a sql id here instead.

Bill,

You can use the runas command with netonly. The...

From books online.

Use the query governor cost limit option to specify an upper limit for the time in which a query can run. Query cost refers to the estimated elapsed...

Try running a trace against the 2000 server and try to compare it with the one against SQL 7.0. Please let us know so that someone here can help you...

Check if you can put the database in emergency mode and try to bcp out all the data.

Only clustering can give you automatic failover capability without human intervention. Replication and Log shipping cannot give you failover capability.

Try re-creating the maintenance plan.