Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase ««123»»

Cardinality Regression Expand / Collapse
Author
Message
Posted Monday, June 2, 2014 1:32 AM
Old Hand

Old HandOld HandOld HandOld HandOld HandOld HandOld HandOld Hand

Group: General Forum Members
Last Login: Monday, August 25, 2014 4:06 AM
Points: 312, Visits: 164
some Confusion..

In the question no where it is mentioned that SQL Server 2014 is running database compatibility level 110
if the database compatibility level of SQL Server 2014 was set to 110 (SQL Server 2012 Compatibility level) then we can use Trace Flag as 2312 and run the query and force to use Cordinal Optimization of compatibility level 120.


Please guide me if I am wrong
Post #1576477
Posted Monday, June 2, 2014 1:40 AM
SSC-Addicted

SSC-AddictedSSC-AddictedSSC-AddictedSSC-AddictedSSC-AddictedSSC-AddictedSSC-AddictedSSC-Addicted

Group: General Forum Members
Last Login: Wednesday, September 17, 2014 3:37 AM
Points: 466, Visits: 609
is msdn confused, or its me....!!!

Nice Question....
Post #1576478
Posted Monday, June 2, 2014 6:20 AM


Ten Centuries

Ten CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen Centuries

Group: General Forum Members
Last Login: Yesterday @ 9:18 AM
Points: 1,398, Visits: 1,640
I respectfully disagree with the answer noted as "correct" by this QOTD.

From the article cited:

5.If your workload is running with database compatibility level 110 and you want to test or run a specific query with the new cardinality estimator, you can run the query with trace flag 2312 to use version 120 (the new version) of the cardinality estimator. To run a query with a trace flag, see the KB article Enable plan-affecting SQL Server query optimizer behavior that can be controlled by different trace flags on a specific-query level.


What's up?
Post #1576544
Posted Monday, June 2, 2014 6:23 AM
Hall of Fame

Hall of FameHall of FameHall of FameHall of FameHall of FameHall of FameHall of FameHall of FameHall of Fame

Group: General Forum Members
Last Login: Yesterday @ 1:57 PM
Points: 3,983, Visits: 3,421
Yeah, this was another one where I had to read BOL a couple times to see what they were trying to say. Thanks for the question.


Tally Tables - Performance Personified
String Splitting with True Performance
Best practices on how to ask questions
Post #1576547
Posted Monday, June 2, 2014 7:40 AM


SSCoach

SSCoachSSCoachSSCoachSSCoachSSCoachSSCoachSSCoachSSCoachSSCoachSSCoachSSCoach

Group: General Forum Members
Last Login: Yesterday @ 9:09 PM
Points: 17,628, Visits: 15,487
batgirl (6/2/2014)
I respectfully disagree with the answer noted as "correct" by this QOTD.

From the article cited:

5.If your workload is running with database compatibility level 110 and you want to test or run a specific query with the new cardinality estimator, you can run the query with trace flag 2312 to use version 120 (the new version) of the cardinality estimator. To run a query with a trace flag, see the KB article Enable plan-affecting SQL Server query optimizer behavior that can be controlled by different trace flags on a specific-query level.


What's up?


The correct answer was based off old documentation that has been since updated. The documentation is correct now and the answer to this question is wrong.




Jason AKA CirqueDeSQLeil
I have given a name to my pain...
MCM SQL Server


SQL RNNR

Posting Performance Based Questions - Gail Shaw
Posting Data Etiquette - Jeff Moden
Hidden RBAR - Jeff Moden
VLFs and the Tran Log - Kimberly Tripp
Post #1576580
Posted Monday, June 2, 2014 7:41 AM


SSCoach

SSCoachSSCoachSSCoachSSCoachSSCoachSSCoachSSCoachSSCoachSSCoachSSCoachSSCoach

Group: General Forum Members
Last Login: Yesterday @ 9:09 PM
Points: 17,628, Visits: 15,487
free_mascot (6/1/2014)
Thank you, Steve. Easy One.


I am curious why you think this was an easy question.




Jason AKA CirqueDeSQLeil
I have given a name to my pain...
MCM SQL Server


SQL RNNR

Posting Performance Based Questions - Gail Shaw
Posting Data Etiquette - Jeff Moden
Hidden RBAR - Jeff Moden
VLFs and the Tran Log - Kimberly Tripp
Post #1576581
Posted Monday, June 2, 2014 8:46 AM


SSCommitted

SSCommittedSSCommittedSSCommittedSSCommittedSSCommittedSSCommittedSSCommittedSSCommitted

Group: General Forum Members
Last Login: Thursday, September 18, 2014 10:35 AM
Points: 1,825, Visits: 2,175
Got it right only because I've been paying attention. And because I answered it without consulting BOL!!

Please don't go. The drones need you. They look up to you.
Connect to me on LinkedIn
Post #1576618
Posted Monday, June 2, 2014 9:04 AM
SSCrazy

SSCrazySSCrazySSCrazySSCrazySSCrazySSCrazySSCrazySSCrazy

Group: General Forum Members
Last Login: Thursday, September 11, 2014 5:55 AM
Points: 2,302, Visits: 560
SQLRNNR (6/2/2014)I am curious why you think this was an easy question.

The fact that it's almost identical to the question posted on 15th May helps!
http://www.sqlservercentral.com/questions/SQL+Server+2014/108889/

The date on that question says 2nd June, so I assume there's a technical glitch somewhere.



Post #1576624
Posted Monday, June 2, 2014 9:13 AM


SSCoach

SSCoachSSCoachSSCoachSSCoachSSCoachSSCoachSSCoachSSCoachSSCoachSSCoachSSCoach

Group: General Forum Members
Last Login: Yesterday @ 9:09 PM
Points: 17,628, Visits: 15,487
richardd (6/2/2014)
SQLRNNR (6/2/2014)I am curious why you think this was an easy question.

The fact that it's almost identical to the question posted on 15th May helps!
http://www.sqlservercentral.com/questions/SQL+Server+2014/108889/

The date on that question says 2nd June, so I assume there's a technical glitch somewhere.


There is that, but since that question the documentation on BOL has been fixed.




Jason AKA CirqueDeSQLeil
I have given a name to my pain...
MCM SQL Server


SQL RNNR

Posting Performance Based Questions - Gail Shaw
Posting Data Etiquette - Jeff Moden
Hidden RBAR - Jeff Moden
VLFs and the Tran Log - Kimberly Tripp
Post #1576628
Posted Monday, June 2, 2014 11:33 AM


Ten Centuries

Ten CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen Centuries

Group: General Forum Members
Last Login: Yesterday @ 9:18 AM
Points: 1,398, Visits: 1,640
SQLRNNR (6/2/2014)
richardd (6/2/2014)
SQLRNNR (6/2/2014)I am curious why you think this was an easy question.

The fact that it's almost identical to the question posted on 15th May helps!
http://www.sqlservercentral.com/questions/SQL+Server+2014/108889/

The date on that question says 2nd June, so I assume there's a technical glitch somewhere.


There is that, but since that question the documentation on BOL has been fixed.


The two questions are actually opposite.

5/15 said I'm running the "old" version (by virtue of compatibility mode), how can I test the "new" version.
6/2 said I'm running the "new" version and it doesn't work, how can I run the "old" version.

Post #1576675
« Prev Topic | Next Topic »

Add to briefcase ««123»»

Permissions Expand / Collapse