The FILESTREAM Data Type in SQL Server 2008

  • Comments posted to this topic are about the item The FILESTREAM Data Type in SQL Server 2008

  • Well written.

  • Good article. A good concept which will help us to solve lot of problems. I have to explore more for advantages and disadvantages.

  • Nice information about FILESTREAM!

    😎

    ============================================================
    SELECT YOUR PROBLEM FROM SSC.com WHERE PROBLEM DESCRIPTION =
    http://www.sqlservercentral.com/articles/Best+Practices/61537/[/url]

  • This is a very usefull artical and I really want to know more about FILESTREAM. just wondering will this files should be on the same server where the SQL is installed? or can it be on a different FileServers?

  • Can the FILESTREAM data type be used in SQL Server 2005?

  • must say very usefull feature of 2k8.

    nicely explained..:)

  • Filestream is only in 2008.

  • samarjit2k1 (9/24/2008)


    Can the FILESTREAM data type be used in SQL Server 2005?

    No just in SQL 2008

    😛

    ============================================================
    SELECT YOUR PROBLEM FROM SSC.com WHERE PROBLEM DESCRIPTION =
    http://www.sqlservercentral.com/articles/Best+Practices/61537/[/url]

  • Deepa:

    Thank you for shedding light on this new data type.

    Can the file be accessed directly from the OS bypassing SQL Server?

    Venki

  • Yes, files can be accessed from the file system.

    But if you modify they might get corrupt & then SQL server might have problem in accessing them.

  • Nice article, but I have a couple of questions/suggestions:

    1. Are there any tests demonstrating the performance difference between FILESTREAM and traditional VARBINARY(MAX) columns? I've seen mention of varbinary being cumbersome in SQL2000 and older, but I was under the impression that it was much better in SQL2005.

    2. Files can be accessed through the file system, but is this recommended? For example, would it be acceptable for a web site to directly access FILESTREAM files on the file system? Or are they just there in case someone wants to manually eye-ball one of them?

    3. How can I convert existing varbinary(max) columns to use FILESTREAM? Will a simple ALTER TABLE do it?

    4. What is the *PRIMARY* motivation for FILESTREAM? Is it for performance, or for accessing DB files from the file system?

    Thanks again for taking the time to write the article. It was very informative and obviously got me thinking.

    Scott

  • What are the advantages of FILESTREAM over the old NTEXT datatype? NTEXT could also be stored in a separate datafile, backed up with SQL Backup, etc.


    Theodore S. Feldman

  • Hi,

    Interesting topic and well written.

    For those who are wondering about achieving the same functionality in SQL Server 2005, it should be possible to use using .NET CLR programming (like writing file handling code in .NET).

    Never tried, but i guess it should be possible.

    Vasant.

  • If that be the case, why would SQL Server permit me to access the file through the OS?

    I would then not be inclined to use this feature, particularly since it will corrupt my database.

Viewing 15 posts - 1 through 15 (of 27 total)

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