Viewing 15 posts - 2,671 through 2,685 (of 49,552 total)
Lynn Pettis (8/9/2016)
Overly complex queries where the optimizer doesn't have time to properly evaluate plans.
That'll get poor plans, not inaccurate row estimations.
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
August 9, 2016 at 9:30 am
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
August 9, 2016 at 9:29 am
A large number of things.
Lack of statistics
Conversions or functions on columns
Table variables (including multi-statement UDFs)
Variables in predicates
Plans being reused for executions with different parameters
Generalising queries (eg the Column = @Parameter...
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
August 9, 2016 at 9:25 am
Pretty much, yes.
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
August 9, 2016 at 4:44 am
What are the exact errors you're getting?
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
August 8, 2016 at 9:00 am
Please don't post multiple threads for the same question.
No replies here. Replies to http://www.sqlservercentral.com/Forums/Topic1807856-3077-1.aspx
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
August 8, 2016 at 8:51 am
By 'composite', I assume you mean a multi-column index.
If so, there's no calculations and the values are stored just as they would be with a single column index.
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
August 8, 2016 at 8:49 am
Jeff Moden (8/7/2016)
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
August 7, 2016 at 12:35 pm
The times for the individual statements within the procedure, not time to read tables.
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
August 7, 2016 at 12:33 pm
VastSQL (8/7/2016)
SQL Server Execution Times:CPU time = 15 ms, elapsed time = 76 ms.
That's the total time for the procedure.
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
August 7, 2016 at 5:58 am
mikes84 (8/6/2016)
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
August 7, 2016 at 5:57 am
Increase your cost threshold. Far too low.
Tune your code, tune your indexes. If the views are nested, fix that first.
Consider some form of reporting server to offload the reports 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
August 6, 2016 at 3:23 pm
rajemessage 14195 (8/6/2016)
should we change to jsaon and leave xml.
No, you should in most cases go for a properly designed normalised data structure.
Otherwise, whether you use json or xml depends...
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
August 6, 2016 at 3:19 pm
The answer to your question is 'maybe', because there's no where near enough information to answer any other way.
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
August 6, 2016 at 3:16 pm
Talking about interviews, I did one last week. The question that tipped the interview from 'maybe' to 'no' was when I asked about the cause of deadlocks and he replied...
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
August 6, 2016 at 3:15 pm
Viewing 15 posts - 2,671 through 2,685 (of 49,552 total)