Once we have copied the files into a different drive, we’ll try to open it, but the OS does not recognize the extension of these files. We copied the above-highlighted objects into different drive. Let us say we just want to copy few files from SQL Server FILESTREAM container to local disk. Instead, it assigns the names as per an internal mechanism. SQL Server does not store the files in their original name. First, we do not know the exact name of the files. Suppose we have the following files stored in the SQL Server FILESTREAM container. Let us first look at the issues with this approach. Even though you might think that we can copy the files directly by accessing the file system.
We might need to copy the complete data or particular data from the file system. Sometimes, we want to export FILESTREAM objects to different drive. In my previous article, Importing SQL Server FILESTREAM data with SSIS packages, we used SSIS packages to import the files into SQL Server FILESTREAM table. It is faster and provides better IO in comparison with the traditional file system. If we have a large number of objects in the file system, it is advisable to use the fast disk for storage purpose. In this series of articles on SQL Server FILESTREAM (see TOC at bottom), we explored various ways to store unstructured data in the file system with the metadata in SQL Server tables.
0 kommentar(er)
