May 19, 2011 at 9:46 pm
Comments posted to this topic are about the item Filestream
May 20, 2011 at 1:44 am
Steve, thanks for the question again.
There is one thing I noticed in your questions-mostly the answer to your question is usually the first choice in the option list 🙂
M&M
May 20, 2011 at 2:28 am
Nice question Steve.
Was the '8.3 NTFS' just a trick?
May 20, 2011 at 2:48 am
Nice question. Had to do some research on 8.3 naming.
Need an answer? No, you need a question
My blog at https://sqlkover.com.
MCSE Business Intelligence - Microsoft Data Platform MVP
May 20, 2011 at 3:08 am
Koen Verbeeck (5/20/2011)
Nice question. Had to do some research on 8.3 naming.
Me too 🙂 Cheers Steve, learnt something new again.
_____________________________________________________________________
[font="Comic Sans MS"]"The difficult tasks we do immediately, the impossible takes a little longer"[/font]
May 20, 2011 at 5:19 am
Nice question; the 8.3 naming red herring made me think hard.
Tom
May 20, 2011 at 5:55 am
If the data is store outside the database this is true but according to the white paper found at http://msdn.microsoft.com/en-us/library/cc949109%28v=sql.100%29.asp Then the limitation does exist as stated in this quote:
Storing BLOB data solely within the database (e.g., using the varbinary(max) data type) is limited to 2 gigabytes (GB) per BLOB.
I hate getting answers wrong and went with the SQL only answer, and wish that the question would be qualified as whether stored solely within the database or not.
Other wise a nice challenging question. :w00t:
Rick Karpel
May 20, 2011 at 6:25 am
Another good question that forced me to refresh my knowledge cache. Thanks Steve.
May 20, 2011 at 6:44 am
Loving The questions Steve, knew it was >2, but the last option made me read after the fact. Always fun to learn something new!
Twitter: @SQLBalls
Blog: http://www.SQLBalls.com
Channel: https://www.youtube.com/@Tales-from-the-Field
May 20, 2011 at 7:09 am
Richard M Karpel (5/20/2011)
If the data is store outside the database this is true but according to the white paper found at http://msdn.microsoft.com/en-us/library/cc949109%28v=sql.100%29.asp Then the limitation does exist as stated in this quote:Storing BLOB data solely within the database (e.g., using the varbinary(max) data type) is limited to 2 gigabytes (GB) per BLOB.
I hate getting answers wrong and went with the SQL only answer, and wish that the question would be qualified as whether stored solely within the database or not.
Other wise a nice challenging question. :w00t:
Uh, I thought FILESTREAM by its very definition was always outside the database files and in the NTFS filesystem....?
May 20, 2011 at 8:19 am
Now if the answer was "No, unless 8.3 naming is enabled in NTFS" you might have gotten me to bite.
Nice question.
May 20, 2011 at 8:49 am
mohammed moinudheen (5/20/2011)
Steve, thanks for the question again.There is one thing I noticed in your questions-mostly the answer to your question is usually the first choice in the option list 🙂
Hmm, have to look at that. I've been trying to put answers in some alpha order, but maybe I've subconsciously switched. For awhile I felt like #3 was always the place I put the correct one :w00t:
May 20, 2011 at 8:53 am
paul s-306273 (5/20/2011)
Nice question Steve.Was the '8.3 NTFS' just a trick?
Yes and no. You can disable 8.3 name creation in NTFS (http://support.microsoft.com/kb/121007), and that is required for FILESTREAM. Or at least recommended since it impacts performance when looking for a unique new name. http://msdn.microsoft.com/en-us/library/cc949109%28v=sql.100%29.aspx
It's a bit of a trick, unintentionally, as it's 8.3 file name creation, not 8.3 naming.
May 20, 2011 at 8:57 am
Richard M Karpel (5/20/2011)
If the data is store outside the database this is true but according to the white paper found at http://msdn.microsoft.com/en-us/library/cc949109%28v=sql.100%29.asp Then the limitation does exist as stated in this quote:Storing BLOB data solely within the database (e.g., using the varbinary(max) data type) is limited to 2 gigabytes (GB) per BLOB.
I hate getting answers wrong and went with the SQL only answer, and wish that the question would be qualified as whether stored solely within the database or not.
Other wise a nice challenging question. :w00t:
The questions was on FILESTREAM data, which is outside the database by definition.
May 20, 2011 at 8:58 am
Richard M Karpel (5/20/2011)
If the data is store outside the database this is true but according to the white paper found at http://msdn.microsoft.com/en-us/library/cc949109%28v=sql.100%29.asp Then the limitation does exist as stated in this quote:Storing BLOB data solely within the database (e.g., using the varbinary(max) data type) is limited to 2 gigabytes (GB) per BLOB.
I hate getting answers wrong and went with the SQL only answer, and wish that the question would be qualified as whether stored solely within the database or not.
Other wise a nice challenging question. :w00t:
I can't get your link to work, so can't check what you referenced there, but the question was about Filestream, which is NOT in the database. That's a major part of the whole point for filestream data. That and faster streaming (NTFS stream instead of SQL Server stream).
- Gus "GSquared", RSVP, OODA, MAP, NMVP, FAQ, SAT, SQL, DNA, RNA, UOI, IOU, AM, PM, AD, BC, BCE, USA, UN, CF, ROFL, LOL, ETC
Property of The Thread
"Nobody knows the age of the human race, but everyone agrees it's old enough to know better." - Anon
Viewing 15 posts - 1 through 15 (of 24 total)
You must be logged in to reply to this topic. Login to reply