Google tells me that Operating System error 21 is "The device is not ready." It's saying that the file can't be accessed at all, not that a couple sectors are...

Take the database into single user mode. That means that no one can access it for the duration of the fix. You may want to shut down sharepoint (if that's...

From redGate's site:

Please note that SQL Log Rescue does not support 64-bit versions of SQL Server or...

Same here.

I am amazed by the patience of some...

How much will you lose by restoring the backup? This is repairable, but you're going to lose what's probably a document. Not easy to say which one.

To offer any real help, I need to see the deadlock graph.

Without that, I can give you generic advice - make sure all your queries are written a optimally as...

SQL does a good job of caching frequently used data in memory, if there's sufficient memory available. If the tables in that database are used often, they will be in...

Why do you need to shrink the log?

Please read through this - Managing Transaction Logs[/url]

Minaz Amin (2/27/2007)

---

1. Backup the transaction log.

2. Shrink it.

3 Create a maintenanace plan to do the...

Switch traceflag 1222 on. That will result in a deadlock graph been written to the error log every time a deadlock occurs. Post the result of that graph here.

DBCC TRACEON(1222,-1)

Ouch.

Firstly, there's a hardware error. You may want to check and even replace the drives. Personally I wouldn't be ahppy about putting a database back on shaky hardware.

There's a single...

The error events. Exception, errorlog, user error message, attention. There may be some others worth checking.

How long are you planning running profiler for?

The message saying the connection was forcefully closed usually means that either the connection was explicitly killed by someone, or the query hit a high severity error and was disconnected.

Both...

SQL will cache frequently used data. If the database is often used, the data will be in memory.

Pintable is still usable on SQL 2005, but it does nothing.

Before you go truncating your transaction log on a regular basis, please note that truncating the log is not a good maintenance practice.

Please read through this - Managing Transaction Logs[/url]

Pity it won't be me.

It took me all of 20 sec or so to find that on google,...