Could have been corruption of the tran log backup, could also have been corruption in the full that you started with.

Restore just the full and run a checkDB on it....

mberry 51447 (6/1/2010)

---

Ok. I have added the indexes. but the first one is a bit wide. I got the following:

Warning! The maximum key length is 900 bytes....

Corruption won't be in the log backups anyway. Log backups contain changes made to the DB and, since the corruption was IO subsystem problems, it would not have been added...

You're thinking of UDFs which behave as cursors in disguise. All a built-in function will...

Maybe, maybe not. But it's not helping the situation at all. There's no way to...

So all the UPPER is doing is preventing index usage. Wonderful. No possibility of getting the query changed?

Ok, this is what I suggest for a first try:

Drop that unique nonclustered...

Please run the following and post the full and complete output.

DBCC CHECKDB (<Database Name>) WITH NO_INFOMSGS, ALL_ERRORMSGS

Rebuilding is not going to help you. From the errors you've posted, your options...

MothInTheMachine (6/1/2010)

---

Sp when i tried to do a restore from the bkp The Restore wizard through an error "The backup set holds a backup of a database other than the...

Not much I can do about that update. Those functions in the where clause are going to kill it, not matter what indexes are there. Is the DB case-sensitive?

What's the...

That's exactly what I was expecting to see. 😉 The no_truncate said backup the log and don't truncate it. That's a option that's used for tail-log backups with a damaged...

What is the exact command that you're running to back the log up?

Monitor the log_reuse for a while, see what values it takes, especially if you can see it just...

Where was the clustered index before you removed it?

Most of those nonclustered indexes are useless, they're too narrow. Other than the queries referenced in the deadlock graph, what other queries...

EXECUTE IMMEDIATE is not a T-SQL command. Remove the IMMEDIATE and it should work fine as-is

Post the deadlock graph please, along with the definition of the table with all indexes, and the exact queries that are deadlocking

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)