June 26, 2014 at 8:58 pm
Comments posted to this topic are about the item What is 268435456?
June 26, 2014 at 9:03 pm
Thanks Andy. It's always good to know a bit of trivia, not that this is a trivial number:-)
June 27, 2014 at 1:04 am
I generally use the below sql for logical name,physical name and path for any db, so this number seemed very familiar, after seeing the question, I have immediately tried the below sql and got the number :-), did not check the other options as the answer is radio button
select * from sys.sysfiles
June 27, 2014 at 1:14 am
pmadhavapeddi22 (6/27/2014)
I generally use the below sql for logical name,physical name and path for any db, so this number seemed very familiar, after seeing the question, I have immediately tried the below sql and got the number :-), did not check the other options as the answer is radio buttonselect * from sys.sysfiles
+1, Nice question. Thanks for sharing
June 27, 2014 at 2:13 am
Thanks Andy for the question.
--rhythmk
------------------------------------------------------------------
To post your question use below link
https://www.sqlservercentral.com/articles/forum-etiquette-how-to-post-datacode-on-a-forum-to-get-the-best-help
🙂
June 27, 2014 at 2:24 am
Related Q.
Where should we *not* find 2147483647 in SQL?
An interesting number! It even has its own Wikipedia page.
June 27, 2014 at 4:31 am
Thank you Andy, nice one and also made it easy for me just two days ago I was looking into the log file's max_size. 🙂
(bit confused: how this value 268435456 is equal to 2TB? I mean through conversion)
ww; Raghu
--
The first and the hardest SQL statement I have wrote- "select * from customers" - and I was happy and felt smart.
June 27, 2014 at 5:30 am
Raghavendra Mudugal (6/27/2014)
(bit confused: how this value 268435456 is equal to 2TB? I mean through conversion)
First line in the answer:
The limit for us humans is 2TB, but SQL stores the limit as the number of 8KB pages!
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
June 27, 2014 at 5:50 am
GilaMonster (6/27/2014)
First line in the answer:The limit for us humans is 2TB, but SQL stores the limit as the number of 8KB pages!
I read that... and also I saw this among other lines in the local_help
"268435456 = Log file will grow to a maximum size of 2 TB."
so all of a sudden I thought that number is being somehow converted to 2TB, but missed to link that those the number of pages of 8000 bytes. now it is clear (268435456 * 8000 = 2147483648000 = 2TB)
Thank you for the pointer, Master. 🙂
ww; Raghu
--
The first and the hardest SQL statement I have wrote- "select * from customers" - and I was happy and felt smart.
June 27, 2014 at 6:52 am
I'm glad you enjoyed the question, wasn't sure how this one would be received;-)
June 27, 2014 at 7:45 am
Much simpler than some of the questions from Andy of late. Really straight forward and is something that should be useful to all DBAs.
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
June 27, 2014 at 8:06 am
Thanks for the question.
June 27, 2014 at 9:27 am
Thanks for the easy question, Andy. I would hate to see a table with 268435456 indexes (let alone 999).
The rhyme was okay. You should have included it in the question. The QotD is supposed to be fun.
June 27, 2014 at 10:24 am
Tried to mix it up on this one! Appreciate all the comments. Think I have a couple more in the pipeline, then I'll work on a new batch and try to avoid all the pitfalls I've learned about so far.
Viewing 15 posts - 1 through 15 (of 26 total)
You must be logged in to reply to this topic. Login to reply