February 12, 2017 at 5:36 am
Comments posted to this topic are about the item Mixed page allocation
Igor Micev,My blog: www.igormicev.com
February 12, 2017 at 6:11 pm
According to the official MS documentation you cited, you are incorrect. Here's the blurb from the first reference you cited...
"This setting is ON for all system databases. tempdbtempdb is the only system database that supports OFF..
That makes both of your answers on TempDB incorrect according to the first reference because TempDB is, in fact, a system database (and they say so!) Now, whether that article is correct or not is a different story.
The second reference tells a different story.
My suggestion would be to only post questions where all the MS documentation is both correct and in agreement. 😉
All that, notwithstanding, great topic! Thanks for taking the time to post it!
--Jeff Moden
Change is inevitable... Change for the better is not.
February 13, 2017 at 12:13 am
e
"This setting is ON for all system databases. tempdb is the only system database that supports OFF..
That makes both of your answers on TempDB incorrect according to the first reference because TempDB is, in fact, a system database (and they say so!) Now, whether that article is correct or not is a different story.
This threw me as well.
This is, however, a great question, had to read up on it, so learned something new.
____________________________________________
Space, the final frontier? not any more...
All limits henceforth are self-imposed.
“libera tute vulgaris ex”
February 13, 2017 at 12:19 am
Jeff Moden - Sunday, February 12, 2017 6:11 PMAccording to the official MS documentation you cited, you are incorrect. Here's the blurb from the first reference you cited..."This setting is ON for all system databases. tempdbtempdb is the only system database that supports OFF..
That makes both of your answers on TempDB incorrect according to the first reference because TempDB is, in fact, a system database (and they say so!) Now, whether that article is correct or not is a different story.
The second reference tells a different story.
My suggestion would be to only post questions where all the MS documentation is both correct and in agreement. 😉
All that, notwithstanding, great topic! Thanks for taking the time to post it!
Great question. I think the summary in this article from the Tiger Team sums up the correct answers nicely: https://blogs.msdn.microsoft.com/sql_server_team/sql-server-2016-changes-in-default-behavior-for-autogrow-and-allocations-for-tempdb-and-user-databases/
February 13, 2017 at 1:09 am
I got it wrong, I was convinced it that although the default for Tempdb was OFF it could still be turned on. Doh!
February 13, 2017 at 1:19 am
Jeff Moden - Sunday, February 12, 2017 6:11 PMAccording to the official MS documentation you cited, you are incorrect. Here's the blurb from the first reference you cited..."This setting is ON for all system databases. tempdbtempdb is the only system database that supports OFF..
That makes both of your answers on TempDB incorrect according to the first reference because TempDB is, in fact, a system database (and they say so!) Now, whether that article is correct or not is a different story.
The second reference tells a different story.
My suggestion would be to only post questions where all the MS documentation is both correct and in agreement. 😉
All that, notwithstanding, great topic! Thanks for taking the time to post it!
Hm, I've missed to check that info in the first reference. However, I tested all the options and they are true as in the QotD.
"This setting is ON for all system databases. tempdb is the only system database that supports OFF". They have probably thought of master, msdb and model for "all system databases", and after they say that only the tempdb supports OFF. Actually semi-correct somehow.
Thanks for spotting this, ... and it should be corrected in the official documentation.
Igor Micev,My blog: www.igormicev.com
February 13, 2017 at 3:03 am
Required a bit of digging - little bit on the obscure side for me, perhaps worth more than a point! Good to read up on though as I had not clocked this setting.
February 13, 2017 at 7:44 am
Description of the argument <mixed_page_allocation_option> ::= in the MSDN ALTER DATABASE is unhappily worded.
A clear explanation is in the MSDN tempdb Database, paragraph Database Options.
Thanks Igor for this question and good explanation.
February 14, 2017 at 1:24 am
Great question, but I think the answer is incorrect.
The first reference states "This setting is ON for all system databases. tempdb is the only system database that supports OFF."
😉
February 14, 2017 at 1:40 am
TjhomasH6610 - Tuesday, February 14, 2017 1:24 AMGreat question, but I think the answer is incorrect.
The first reference states "This setting is ON for all system databases. tempdb is the only system database that supports OFF."
😉
I get it wrong because of this sentence. But, if you try to change it, you get an error.
Thanks, Igor!
February 14, 2017 at 6:15 am
I got it wrong as well. This is what happens when the official documentation is written like it is. Oh well...I learned something new so it was worth it.
March 30, 2017 at 2:31 pm
Jeff Moden - Sunday, February 12, 2017 6:11 PMMy suggestion would be to only post questions where all the MS documentation is both correct and in agreement. 😉
That is kind of a big ask.
Jason...AKA CirqueDeSQLeil
_______________________________________________
I have given a name to my pain...MCM SQL Server, MVP
SQL RNNR
Posting Performance Based Questions - Gail Shaw[/url]
Learn Extended Events
Viewing 12 posts - 1 through 11 (of 11 total)
You must be logged in to reply to this topic. Login to reply