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

FILESTREAM storage requirement Expand / Collapse
Posted Thursday, May 20, 2010 7:03 AM
SSC Eights!

SSC Eights!SSC Eights!SSC Eights!SSC Eights!SSC Eights!SSC Eights!SSC Eights!SSC Eights!

Group: General Forum Members
Last Login: Today @ 1:55 AM
Points: 911, Visits: 682


Abhijit -
Post #925082
Posted Saturday, May 22, 2010 6:27 AM
UDP Broadcaster

UDP BroadcasterUDP BroadcasterUDP BroadcasterUDP BroadcasterUDP BroadcasterUDP BroadcasterUDP BroadcasterUDP Broadcaster

Group: General Forum Members
Last Login: Tuesday, April 15, 2014 3:14 AM
Points: 1,487, Visits: 1,687
@PaulRandal writes a excellent article..

Isolation Semantics

The isolation semantics are governed by database engine transaction isolation levels. When FILESTREAM data is accessed through the Win32 APIs, only the read-committed isolation level is supported. Transact-SQL access also allows the repeatable-read and serializable isolation levels. Furthermore, using Transact-SQL access, dirty reads are permitted through the read-uncommitted isolation level, or the NOLOCK query hint, but such access will not show in-flight updates of FILESTREAM data.

The file system access open operations do not wait for any locks. Instead, the open operations fail immediately if they cannot access the data because of transaction isolation. The streaming API calls fail with ERROR_SHARING_VIOLATION if the open operation cannot continue because of isolation violation.
Post #926407
Posted Sunday, May 30, 2010 1:03 AM


Group: General Forum Members
Last Login: Tuesday, December 24, 2013 4:42 AM
Points: 460, Visits: 2,523
The 'WHY' part is still a mystery and one possible reason could be the way SNAPSHOT isolation works. Under snapshot isolation level, your transaction should be able to read a snapshot of the database as of the time when the transaction starts. For the NON-FILESTREAM data, SQL Server implements this by keeping versions of the data in tempdb database.

When it comes to the FILESTREAM data, which is stored in the NTFS - not in the table - and which may be huge blob files, this may not be a trivial task to implement a similar versioning mechanism.

That '**could be**' be the reason why SNAPSHOT isolation is not supported with FILESTREAM.

Post #930118
« Prev Topic | Next Topic »

Add to briefcase

Permissions Expand / Collapse