Click here to monitor SSC
SQLServerCentral is supported by Red Gate Software Ltd.
 
Log in  ::  Register  ::  Not logged in
 
 
 
        
Home       Members    Calendar    Who's On


Add to briefcase 12»»

FILESTREAM Data Expand / Collapse
Author
Message
Posted Tuesday, March 24, 2009 10:17 PM
Hall of Fame

Hall of FameHall of FameHall of FameHall of FameHall of FameHall of FameHall of FameHall of FameHall of Fame

Group: General Forum Members
Last Login: Thursday, September 25, 2014 1:21 PM
Points: 3,143, Visits: 139
Comments posted to this topic are about the item FILESTREAM Data
Post #683023
Posted Wednesday, March 25, 2009 2:05 AM
SSCrazy

SSCrazySSCrazySSCrazySSCrazySSCrazySSCrazySSCrazySSCrazy

Group: General Forum Members
Last Login: Yesterday @ 1:46 PM
Points: 2,604, Visits: 572
I think this is an Incorrect question! How do you update the FILESTREAM column without updating the row?

Håkan Winther


/Håkan Winther
MCITP:Database Developer 2008
MCTS: SQL Server 2008, Implementation and Maintenance
MCSE: Data Platform
Post #683109
Posted Wednesday, March 25, 2009 2:43 AM


SSCertifiable

SSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiable

Group: General Forum Members
Last Login: Yesterday @ 3:07 AM
Points: 6,040, Visits: 8,322
I have to disagree with half of the answer key.

First: The third statement ("when data in a FILESTREAM column is updated, the data in the filestream file is updated") is of course true. Otherwise, the updates would have been lost. How the update is performed (only rewrite changed bytes or rewrote complete content) is an implementation detail. From the answer key, I gather the intent was to check if we know that particular implementation detail, but that was far from clear from the question. Deleting and rewriting the content is a way to update the data in the filestream file, after all. If the statement would have been written as "when data in a FILESTREAM column is partially updated, only the modified data in the filestream file is updated", then I would have agreed.

Second: The second statement ("the NTFS partition that holds filestream data should have generation of 8.3 names and last access time tracking disabled") is ambiguous, at best. I'm not a native English speaker, but as far as I know "should" can have two meanings in this context: "must", or "recommended". With the first interpretation, this statement is completely false - FILESTREAM will work just fine without disabling these Windows options. With the second interpretation, it's less clear cut, but I still find the statement too strong. The white paper the answer key references recommends disabling these options for performance, but (a) only if the amount of files in the directory becomes very large (300,000 or more - easily achieved if a FILESTREAM column is in the "Customers" table, but defnitely not if it's in the "Products" or "Branches" table...), and (b) not if there are other applications running on the same box that require 8.3 filenames.

So either you interpret "should" as "must", in which case the second statement is false, or you interpret "should" as "recommended", in which case the second statement is a somewhat good, but too strong recommendation that lacks the imporant caveats, so still false.

The correct answer to this QotD is that the first, third and fourth statements are true, and the second statement is false. Which is what (at this time) the majority of respondents have answered.



Hugo Kornelis, SQL Server MVP
Visit my SQL Server blog: http://sqlblog.com/blogs/hugo_kornelis
Post #683117
Posted Wednesday, March 25, 2009 4:02 AM
SSCommitted

SSCommittedSSCommittedSSCommittedSSCommittedSSCommittedSSCommittedSSCommittedSSCommitted

Group: General Forum Members
Last Login: Thursday, October 16, 2014 2:38 AM
Points: 1,669, Visits: 2,102
I agree with the first point the question is badly structured and I clear as to what was being asked. However point two, I'm not so sure about

http://msdn.microsoft.com/en-us/library/cc949109.aspx

states
"There are two NTFS options that need to be configured to facilitate FILESTREAM performance....
The first configuration option is to disable the generation of 8.3 names when new files are created (or renamed)."

should != must

Ian

Post #683152
Posted Wednesday, March 25, 2009 7:47 AM
SSCrazy

SSCrazySSCrazySSCrazySSCrazySSCrazySSCrazySSCrazySSCrazy

Group: General Forum Members
Last Login: Monday, April 6, 2009 1:29 PM
Points: 2,057, Visits: 215
I agree with Hugo that whether you update part of a file or re-write the entire file, the data in the file is updated. The bits may be in a different location, but it is the same file.
Post #683306
Posted Wednesday, March 25, 2009 8:05 AM
Hall of Fame

Hall of FameHall of FameHall of FameHall of FameHall of FameHall of FameHall of FameHall of FameHall of Fame

Group: General Forum Members
Last Login: Thursday, September 25, 2014 1:21 PM
Points: 3,143, Visits: 139
I apologize for not being able to give this forum the attention you all deserve.

My Mother is in the hospital and gets out today. I must bring her to my house.

)
Post #683317
Posted Wednesday, March 25, 2009 11:37 AM


SSCertifiable

SSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiableSSCertifiable

Group: General Forum Members
Last Login: Tuesday, October 14, 2014 10:58 AM
Points: 5,333, Visits: 25,272
From the Encarata dictionary
Update (transitive verb)
to provide somebody or something with the most recent information or with more recent information than was previously available


The data in the filestream file IS for all practical purposes changed i.e., updated. What is the mechanism of how that task is accomplished, is the real question we are quibbling about

It is accomplished by writing the new content to a new file, but this new files file name / identification is NOT changed.

My heart goes out to Dr. Diana Dee and Steve Jones, as I well know that framing the QOD is not a simple task, and I do disagree with the questioners designation of which answer is incorrect


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

Ron

Please help us, help you -before posting a question please read

Before posting a performance problem please read
Post #683517
Posted Wednesday, March 25, 2009 11:43 AM


SSC-Dedicated

SSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-DedicatedSSC-Dedicated

Group: Administrators
Last Login: Today @ 4:56 PM
Points: 31,168, Visits: 15,612
I have updated the question to mark #3 as correct. Not sure how I missed that.

I disagree with Hugu. In English, to me, a "should" implies a recommendation. That would fit with recommendations I've seen in that white paper.

I have returned points to people answering up to this point.







Follow me on Twitter: @way0utwest

Forum Etiquette: How to post data/code on a forum to get the best help
Post #683522
Posted Wednesday, March 25, 2009 1:27 PM
Ten Centuries

Ten CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen Centuries

Group: General Forum Members
Last Login: Monday, September 8, 2014 3:51 PM
Points: 1,426, Visits: 734
I disagree with the inclusion of #3 being correct. The "FILESTREAM file" is not updated but is replaced with a new file.

from the referenced artical:
"Whenever a FILESTREAM file is opened for a write operation, a new zero-length file is created and the entire updated FILESTREAM data value is written to it. The old file is removed asynchronously as described in the “Configuring FILESTREAM Garbage Collection” section later in this white paper."
Post #683610
Posted Thursday, March 26, 2009 11:00 AM
Ten Centuries

Ten CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen CenturiesTen Centuries

Group: General Forum Members
Last Login: Friday, August 10, 2012 6:08 PM
Points: 1,156, Visits: 801
Having not had the chance or reason yet to use FileStream data in SQL Server, I found the question and the discussion enlightening, and intriguing. Thanks!
Post #684386
« Prev Topic | Next Topic »

Add to briefcase 12»»

Permissions Expand / Collapse