17.07.2015 Views

The Art of SQL Server FILESTREAM - Red Gate Software

The Art of SQL Server FILESTREAM - Red Gate Software

The Art of SQL Server FILESTREAM - Red Gate Software

SHOW MORE
SHOW LESS

You also want an ePaper? Increase the reach of your titles

YUMPU automatically turns print PDFs into web optimized ePapers that Google loves.

Chapter 12: Planning, Configuration and Best PracticesAccess to <strong>FILESTREAM</strong> data from a remote computer uses the <strong>Server</strong> Message Block(SMB) protocol. SMB is a protocol used for sharing files and other resources such asprinters between computers. <strong>The</strong> default port number used by SMB is 445. You need tomake sure that the firewall is configured to allow access to these ports.Configuring the client computer for remote accessNote that streaming access to the <strong>FILESTREAM</strong> data is available only when the clientis authenticated using Windows authentication. So, when accessing <strong>FILESTREAM</strong> dataremotely, it is very important to ensure that the Windows user account your applicationuses on the other computer has adequate permissions to log in to the <strong>SQL</strong> <strong>Server</strong> instanceand access the <strong>FILESTREAM</strong> table using Windows authentication (Integrated Security).As on the server side, to use <strong>FILESTREAM</strong> in a firewall-protected environment, the clientmust be able to resolve DNS names to the server that contains the <strong>FILESTREAM</strong> files.Configuring the client application for remote accessOn the application side, accessing <strong>FILESTREAM</strong> data remotely is no different fromaccessing it from the same computer. In Chapter 3, we saw several examples that demonstratedhow to access the <strong>FILESTREAM</strong> data using the streaming APIs. You should be ableto run those examples successfully against a remote <strong>SQL</strong> <strong>Server</strong> instance if <strong>FILESTREAM</strong>has been correctly configured for remote access.MSDN documentation recommends doing fewer updates with bigger data chunks whenaccessing <strong>FILESTREAM</strong> data remotely. <strong>The</strong> recommended buffer size is 60 KB for theoptimum performance.450

Hooray! Your file is uploaded and ready to be published.

Saved successfully!

Ooh no, something went wrong!