Note that there are some explanatory texts on larger screens.

plurals
  1. PO
    text
    copied!<p>Is there a reason why you want to get the files out of the database in the first place?</p> <p>How about still saving them in SQL Server, but using a <a href="http://msdn.microsoft.com/en-us/library/gg471497.aspx" rel="nofollow"><code>FILESTREAM</code> column</a> instead of <code>IMAGE</code>?</p> <p>Quote from the link:</p> <blockquote> <p>FILESTREAM enables SQL Server-based applications to store unstructured data, such as documents and images, on the file system. Applications can leverage the rich streaming APIs and performance of the file system and at the same time maintain transactional consistency between the unstructured data and corresponding structured data.</p> <p>FILESTREAM integrates the SQL Server Database Engine with an NTFS file system by storing varbinary(max) binary large object (BLOB) data as files on the file system. Transact-SQL statements can insert, update, query, search, and back up FILESTREAM data. Win32 file system interfaces provide streaming access to the data.</p> <p>FILESTREAM uses the NT system cache for caching file data. This helps reduce any effect that FILESTREAM data might have on Database Engine performance. The SQL Server buffer pool is not used; therefore, this memory is available for query processing.</p> </blockquote> <p>So you would get the best out of both worlds:<br> The files would be stored as files on the hard disk (probabl faster compared to storing them in the database), but you don't have to care about file shares, permissions etc.</p> <p>Note that you need at least SQL Server 2008 to use <code>FILESTREAM</code>.</p>
 

Querying!

 
Guidance

SQuiL has stopped working due to an internal error.

If you are curious you may find further information in the browser console, which is accessible through the devtools (F12).

Reload