September 26, 2013 at 8:27 pm
Comments posted to this topic are about the item Filestream data
September 26, 2013 at 8:27 pm
September 26, 2013 at 11:02 pm
bitbucket-25253 (9/26/2013)
Nice question to end the week ............
+1 🙂
_______________________________________________________________
To get quick answer follow this link:
http://www.sqlservercentral.com/articles/Best+Practices/61537/
September 26, 2013 at 11:35 pm
nice question,,,, learned something.
September 26, 2013 at 11:38 pm
Didn't even have to think for this one. Which is nice for a Friday 😀
Need an answer? No, you need a question
My blog at https://sqlkover.com.
MCSE Business Intelligence - Microsoft Data Platform MVP
September 27, 2013 at 12:24 am
Koen Verbeeck (9/26/2013)
Didn't even have to think for this one. Which is nice for a Friday 😀
Same here. After long long time, I didn't had to think twice. Happy weekend. Cheers... 🙂
September 27, 2013 at 12:28 am
Don't often use FILESTREAM so was nice to h ave to go and do some 'forced' reading on it.
Thanks
Hope this helps...
Ford Fairlane
Rock and Roll Detective
September 27, 2013 at 12:57 am
Perfect qotd and explanation.
Thanks!
September 27, 2013 at 1:03 am
Easy one. Thanks.
Just to close the gaps, the option should have been VARBINARY(MAX) instead of just VARBINARY because anything else like VARBINARY(N) {N being a natural number up to 8000} won't work but the explanation covers it nicely. 🙂
create table #t(i VARBINARY(8000) FILESTREAM)
Incorrect syntax near 'FILESTREAM'.
September 27, 2013 at 1:36 am
This was removed by the editor as SPAM
September 27, 2013 at 3:06 am
reminds me of a session at this years SQLBits 🙂
September 27, 2013 at 3:19 am
What I found even more interesting:
"The standard varbinary(max) limitation of 2-GB file sizes does not apply to BLOBs that are stored in the file system."
The file size is then, as I understood, only restricted by NTFS. Which could mean: We are already able to store documents bigger than 2 GB into SQL Server. THAT was the most interesting thing for me!
That might explain why NVARCHAR(max) or VARCHAR(max) does not apply: It is not implemented for those data types. Wouldn't be necessary anyway, I know.
Nice question, Steve: Thanks!
________________________________________________________
If you set out to do something, something else must be done first.
September 27, 2013 at 5:21 am
"FILESTREAM, of course" has 11%, so that was a bit sneaky!
September 27, 2013 at 7:18 am
+1 to the excellent question comments 🙂
September 27, 2013 at 8:17 am
This was one of the SQL Server questions in the MS Exams when I wrote it few years ago 🙂
Viewing 15 posts - 1 through 15 (of 24 total)
You must be logged in to reply to this topic. Login to reply