If you are installing SQL Server 2008 in ‘Unattended mode’, you can use /FILESTREAMLEVEL and /FILESTREAMSHARENAME configuration options to configure FILESTREAM features. Allow remote clients to have streaming access to FILESTREAM dataĮnabling FILESTREAM during an Unattended installation.Enable FILESTREAM for file I/O streaming access.Enable FILESTREAM for Transact-SQL access.This tab allows you to specify the FILESTREAM configuration options that you wish to enable on your new SQL Server Instance.įILESTREAM feature may be enabled with three different levels of access to the FILESTREAM data, namely: You will see a new tab labeled “FILESTREAM” on the “Database Engine Configuration” page of the installation wizard. The easiest way to enable FILESTREAM feature is to do so as part of the installation process. Enabling FILESTREAM as part of installation If the SQL Server 2008 instance is already installed without FILESTREAM feature, it can still be enabled following the steps explained later in this section. It is quite easy to enable the FILESTREAM feature as part of a new SQL Server 2008 installation. The default installation of SQL Server 2008 disables FILESTREAM feature. SQL Server ensures transactional consistency between the FILESTREAM data stored in the NT file system and the structured data stored in the tables. When the FILESTREAM attribute is set, SQL Server stores the BLOB data in the NT file system and keeps a pointer the file, in the table. The size of the file is limited by the size of the disk volume only. A VARBINARY (MAX) column with FILESTREAM attribute is not restricted to the 2 GB limit SQL Server imposes on Large Value Types. Any data that you store in such columns will be stored in the NT file system as a disk files and a pointer to the disk file is stored in the table. When the FILESTREAM attribute of a VARBINARY (MAX) column is set, it becomes a ‘FILESTREAM enabled’ column. FILESTREAM is not a data type instead, it is an attribute that can be assigned to a VARBINARY (MAX) column. The term ‘FILESTREAM data type’ or ‘FILESTREAM column’ is very commonly used and it gives an indication that the FILESTREAM feature is implemented as a data type. When accessing FILESTREAM data through the streaming API, SQL Server buffer pool is not used and hence it does not reduce the amount of memory available for Database Engine query processing. This minimizes the effect that FILESTREAM data might have on the Database Engine performance. FILESTREAM uses NT System Cache for caching file data. Storing BLOB data in NT file system, allows SQL Server to take advantage of the NTFS I/O streaming capabilities and at the same time, maintain transactional consistency of the data. The FILESTREAM feature allows storing BLOB data (example: word documents, image files, music and videos etc) in the NT file system and ensures transactional consistency between the unstructured data stored in the NT file system and the structured data stored in the table. FILESTREAM FeatureįILESTREAM was introduced in SQL Server 2008 for the storage and management of unstructured data. Moreover management (backup, restore, security etc) of the data will be a pain too. This approach was found to be good in terms of performance, but does not ensure transactional consistency. The other approach is to store the unstructured data as disk files and store the location of the file in the table along with the other structured data linked to it. This ensures transactional consistency and reduces management complexities, but is bad for performance. One approach suggests storing the data in a VARBINARY or IMAGE column. Before then, there were two approaches to storing unstructured data in SQL Server. Storing and managing unstructured data was tricky prior to the release of SQL Server 2008.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. ArchivesCategories |