I don't know if this is part of the problem:

Note SQL Server 7.0 system databases are not compatible with SQL Server 2000. Do not attach SQL Server 7.0 master, model,...

As Phil pointed out .mdf/.ldf files are not your normal backups and cannot be 'restored'. You can use Phil's method to attach the files or use the sp_attach_db command (refer...

If your database is in FULL recovery mode, you need to be doing full AND log backups.

-SQLBill

After you run the shrinkfile command, you need to run DBCC UPDATEUSAGE command. Refer to the BOL for the proper syntax.

-SQLBill

After you delete the transaction log, do you do a Full Backup? If not, then the transaction log backups are worthless to you. Deleting the .ldf

'breaks the restore...

DATETIMEs are NOT stored in any 'date' recognizable format. They are not stored as 1/20/2006, 20/1/2006, or 2006-01-20. They are stored as bits. It is the front end that translates...

Why are you deleting the transaction log? This is really not a good thing to do and should only be done in emergencies.

If you don't need the transaction log for...

1. You say you installed the client tools...do you have a database installed somewhere?

2. Where is the database installed? Can you go to that system and log into the database?

3....

I would guess that you would have something like a SUS server. That is the 'central' update server. It gets all the updates (such as from Microsoft) and then distributes...

Something else to check.....is this extra space in the Data files or the log files?

Is your database in FULL Recovery Mode or SIMPLE Recovery Mode? If in FULL Recovery Mode...

You are probably using Windows Firewall. If so, it blocks the SQL Server ports by default (1433 and 1434).

Check that first. Next do you have a login on the...

It's probably an issue of you doing the backup to the same disk(s) as the database. It's trying to read from AND write to the same drives at the same...

Refer to the BOL, use the index tab, enter RESTORE DATABASE, then choose the option that says Transact SQL.

Basically, you need to run the RESTORE like this:

RESTORE DATABASE dbname

FROM .....

WITH...

Lots of reasons.......are you doing database maintenance, such as reindexing? That will cause it to grow to a large size.

-SQLBill

You have other problems......I backup a 200+ GB database every day (full backup) and it doesn't have any affect on the server.

Maybe your system isn't powerful enough? Maybe you have...