Viewing 15 posts - 32,641 through 32,655 (of 49,552 total)
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....
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
June 1, 2010 at 11:31 pm
mberry 51447 (6/1/2010)
Warning! The maximum key length is 900 bytes....
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
June 1, 2010 at 11:47 am
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...
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
June 1, 2010 at 11:46 am
Brandie Tarvin (6/1/2010)
It most instances, it can turn a set based query into a RBAR query
You're thinking of UDFs which behave as cursors in disguise. All a built-in function will...
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
June 1, 2010 at 11:15 am
mberry 51447 (6/1/2010)
But somehow I dont believe that use of the UPPER function is causing this.
Maybe, maybe not. But it's not helping the situation at all. There's no way to...
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
June 1, 2010 at 11:14 am
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...
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
June 1, 2010 at 11:12 am
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...
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
June 1, 2010 at 11:04 am
MothInTheMachine (6/1/2010)
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
June 1, 2010 at 10:11 am
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...
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
June 1, 2010 at 9:47 am
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...
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
June 1, 2010 at 9:33 am
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...
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
June 1, 2010 at 9:22 am
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...
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
June 1, 2010 at 9:21 am
EXECUTE IMMEDIATE is not a T-SQL command. Remove the IMMEDIATE and it should work fine as-is
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
June 1, 2010 at 8:46 am
Post the deadlock graph please, along with the definition of the table with all indexes, and the exact queries that are deadlocking
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
June 1, 2010 at 8:44 am
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)
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
June 1, 2010 at 8:32 am
Viewing 15 posts - 32,641 through 32,655 (of 49,552 total)