Viewing 15 posts - 44,371 through 44,385 (of 49,552 total)
Jeffrey Williams (9/19/2008)
Just a guess, but I think you'll find that the difference in the execution plans is due to your production system escalating to a parallel plan.
I'm thinking much...
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
September 19, 2008 at 3:25 pm
If you run a select under the default isolation level (read committed), the lock taken will prevent any changes to the table while the select is running (insert, update, delete),...
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
September 19, 2008 at 3:18 pm
What's the fragmentation on that index and the clustered index like?
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
September 19, 2008 at 3:18 pm
You may want to contact customer support on this. It sounds like a bug.
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
September 19, 2008 at 2:29 pm
avipenina (9/19/2008)
both server was restart so the execution plan on both are from scratch.
Doesn't mean they'll be the same. Please look at the exec plan on the two servers 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
September 19, 2008 at 2:28 pm
Inside SQL Server 2005: The storage engine goes into a fair bit of detail on the storage engine.
The Guru's guide to SQl Architecture and internals has a lot of info...
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
September 19, 2008 at 9:30 am
SQL triggers fire once per operation, not once per row. SQL doesn't have row-triggers.
Cursors in a trigger are a near-guarantee of poor performance and potential deadlocks. Triggers should be written...
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
September 19, 2008 at 9:24 am
And make sure that the SQL service and SQL Agent are shut down.
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
September 19, 2008 at 9:20 am
Shark Energy (9/19/2008)
Is it just me or was some of the advice in this topic very very risky?
It's not just you. Some were more than 'very risky'
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
September 19, 2008 at 9:15 am
Odd. That message indicates a forced disconnect (a kill command, or an error of severity 20 or higher) or a network glitch.
A kill or severe error should show up...
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
September 19, 2008 at 9:14 am
Run perfmon and monitor from there. I normally just run it directly from the run dialog or command line.
For the databases counters you should see something like the attached...
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
September 19, 2008 at 9:13 am
If ALLOW_PAGE_LOCKS is off, then SQL will not take page locks on that index. It will only take locks at the row or table level.
IF ALLOW_ROW_LOCKS is off, then SQL...
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
September 19, 2008 at 9:11 am
When you set up the counters you can specify which DB it's for, or specify counters for all databases overall.
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
September 19, 2008 at 6:58 am
Developer (as it's name implies) is licenced for development usage only. I would suggest you replace the version on the test server with dev edition and put standard edition...
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
September 19, 2008 at 6:57 am
jcrawf02 (9/19/2008)
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
September 19, 2008 at 6:49 am
Viewing 15 posts - 44,371 through 44,385 (of 49,552 total)