The final
directory listed (Resumes, in the example) is created automatically; the rest of the
directories must already exist. Within the base directory, SQL Server 2008 places a
filestream.hdr file and a subfolder called $FSLOG. SQL Server 2008 uses these to
control the FILESTREAM data and ensure transactional consistency when working with
FILESTREAM data. When SQL Server is running, all FILESTREAM directories are locked and
controlled only by SQL Server.
How does the ability to store large objects as files in the operating system affect the
disaster recovery landscape? For starters, you need to take care not to allow users to
manipulate those files outside of the context of SQL Server. Also, when the database is
backed up and later restored, all of the FILESTREAM data moves along with it. Finally, since
a FILESTREAM is represented within SQL Server as a filegroup, it is possible to include or
exclude that FILESTREAM from a complex filegroup backup/recovery plan, to use piecemeal
restore, and so on. This ability to include or exclude data from backups is a
significant improvement when it comes to working with binary data.
Pages:
585
586
587
588
589
590
591
592
593
594
595
596
597
598
599
600
601
602
603
604
605
606
607
608
609