Home/ Questions/Q 519623
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-13T08:03:37+00:00

I had some questions around the FILESTREAM capability of SQL Server 2008. What would

  • 0

I had some questions around the FILESTREAM capability of SQL Server 2008.

  1. What would the difference in performance be of returning a file streamed from SQL Server 2008 using the FILESTREAM capability vs. directly accessing the file from a shared directory?

  2. If 100 users requested 100 100Mb files (stored via FILESTREAM) within a 10 second window, would SQL Server 2008 performance slow to a crawl?

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    If 100 users requested 100 100Mb files (stored via FILESTREAM) within a 10 second window, would SQL Server 2008 performance slow to a crawl?

    On what kind of a server?? What kind of hardware to serve those files? What kind of disks, network etc.?? So many questions…….

    There’s a really good blog post by Paul Randal on SQL Server 2008: FILESTREAM Performance – check it out. There’s also a 25-page whitepaper on FILESTREAM available – also covering some performance tuning tips.

    But also check out the Microsoft Research TechReport To BLOB or Not To BLOB.

    It’s a very profound and very well based article that put all those questions through their paces.

    Their conclusion:

    The study indicates that if objects
    are larger than one megabyte on
    average    , NTFS has a clear advantage
    over SQL Server. If the objects are
    under 256 kilobytes, the database has
    a clear advantage    . Inside this range,
    it depends on how write intensive the
    workload is, and the storage age of a
    typical replica in the system.

    So judging from that – if your blobs are typically less than 1 MB, just store them as a VARBINARY(MAX) in the database. If they’re typically larger, then just the FILESTREAM feature.

    I wouldn’t worry so much about performance rather than other benefits of FILESTREAM over “unmanaged” storage in a NTFS file folder: storing files outside the database without FILESTREAM, you have no control over them:

    • no access control provided by the database
    • the files aren’t part of your SQL Server backup
    • the files aren’t handled transactionally, e.g. you could end up with “zombie” files which aren’t referenced from the database anymore, or “skeleton” entries in the database without the corresponding file on disk

    Those features alone make it absolutely worthwhile to use FILESTREAM.

    • 0