The Art of SQL Server FILESTREAM - Red Gate Software

Chapter 11: FileTableAs a best practice, consider writing code that is independent from the SQL Serverconfiguration by using relative paths. If you are storing path values anywhere, store thevalue relative to the database-level directory. That way, a change to the configuration ofSQL Server will not break the application.You may be storing path values as part of an application's configuration data, whichmight allow the application to retrieve the folder where all order files are located. Toavoid storing the full path: \\servername\MSSQLSERVER\NorthPole\Documents\Order Files store instead: \Order Files. Then, when the full path is needed, call theFileTableRootPath() function and concatenate your stored value to the return valueof the function.A more comprehensive discussion of the use of .NET file I/O APIs is beyond the scope ofthis book. However, below are some limitations that exist in the use of the APIs.• It's not possible to rename the database or FileTable root directories usingthe I/O APIs.• It's not possible to obtain an exclusive handle on the database or FileTableroot directories.Managing FileTablesIn addition to the functions and views that apply to all FILESTREAM-enabled databasesand tables, there are specific functions and views added to SQL Server 2012 to support theFileTable feature.T-SQL functionsIn addition to the PathName() function, which has existed since SQL Server 2008,three new documented T-SQL functions have been added to SQL Server 2012:FileTableRootPath(), GetFileNamespacePath() and GetPathLocator().423