Filestream data

  • Comments posted to this topic are about the item Filestream data

  • Nice question to end the week ............

    If everything seems to be going well, you have obviously overlooked something.

    Ron

    Please help us, help you -before posting a question please read[/url]
    Before posting a performance problem please read[/url]

  • 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/

  • nice question,,,, learned something.

  • 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

  • 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... 🙂

  • 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

  • Perfect qotd and explanation.

    Thanks!

  • 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'.

  • This was removed by the editor as SPAM

  • reminds me of a session at this years SQLBits 🙂

  • 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.

  • "FILESTREAM, of course" has 11%, so that was a bit sneaky!

  • +1 to the excellent question comments 🙂

  • 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 25 total)

You must be logged in to reply to this topic. Login to reply