Viewing 15 posts - 15,976 through 15,990 (of 49,552 total)
No, fragmentation will not cause deadlocks, neither will removing fragmentation resolve deadlocks.
Most likely the reason the deadlocks have gone away is that the rebuild also updates stats, which invalidates execution...
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
October 22, 2012 at 9:15 am
Remove the GO. It is not a T-SQL command, it's a batch-breaker for the client app (SSMS).
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
October 22, 2012 at 9:10 am
Melktert! Awesome (well, when made properly). Apple. Lemon meringue (lemon slightly sour, meringue sweet)
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
October 22, 2012 at 8:48 am
What is the exact command you're trying to run there? What's in the .sql file?
Looks like you're trying to issue a shrink command against a log file that does not...
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
October 22, 2012 at 8:24 am
I would guess because backup statements are checked for validity when they run. Two very different statements, you shouldn't be surprised they act differently (one's DDL the other maintenance)
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
October 22, 2012 at 8:22 am
Please don't hijack other people's threads. Start your own thread with this problem.
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
October 22, 2012 at 8:21 am
Nope. Simple recovery is not the reason for the high recovery time. You either had huge uncommitted transactions when the DB shut down or you have severe log fragmentation or...
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
October 22, 2012 at 8:19 am
Because the validity of the statement is checked before it's actually run.
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
October 22, 2012 at 6:50 am
It depends, no simple answer here.
Multiple files on the same RAID array, whether it be in the same filegroup or in different filegroups - no effect.
Multiple files on different RAID...
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
October 22, 2012 at 5:06 am
Just a general point... SQL Server and AI generally don't go together. Oh, it's possible, I've written a GA framework in SQL, but it's not usually efficient. Maybe consider sticking...
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
October 22, 2012 at 2:11 am
Yes, the claim in the book is incorrect and is a common myth.
p.s. Your second will be able to use indexes, but probably for a scan operation, not a seek...
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
October 22, 2012 at 12:44 am
Several valid reasons, root being that the nonclustered index wasn't covering therefore wasn't efficient. Probably a hash or merge join, those don't use indexes. (btw, that predicate technically is not...
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
October 21, 2012 at 11:52 am
Firstly, there isn't a problem here. There is never a guarantee that identity values will not have gaps. Any time there's a insert that rolls back, the identity increments and...
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
October 21, 2012 at 11:28 am
SqlUser-369680 (10/21/2012)
What is the best approach to this problem?
Please read the book chapter that I referenced.
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
October 21, 2012 at 6:45 am
SQLWorks (10/21/2012)
He did say "dirty read is no problem at all"...
Yes, but in my experience most people who say that don't realise what that means. It's not just a case...
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
October 21, 2012 at 6:30 am
Viewing 15 posts - 15,976 through 15,990 (of 49,552 total)