﻿<?xml version='1.0' encoding='UTF-8'?><rss version="2.0" xmlns:dc="http://purl.org/dc/elements/1.1/"><channel><title>SQLServerCentral / Article Discussions / Discuss content posted by Deepa Parikh / Article Discussions by Author  / 8.3 filenames and FILESTREAM / Latest Posts</title><generator>InstantForum.NET v2.9.0</generator><description>SQLServerCentral</description><link>http://www.sqlservercentral.com/Forums/</link><webMaster>notifications@sqlservercentral.com</webMaster><lastBuildDate>Thu, 20 Jun 2013 02:12:04 GMT</lastBuildDate><ttl>20</ttl><item><title>RE: 8.3 filenames and FILESTREAM</title><link>http://www.sqlservercentral.com/Forums/Topic575303-538-1.aspx</link><description>Thanks for the great tipSomething to keep in mind for future FILESTREAM implementation</description><pubDate>Thu, 25 Sep 2008 10:56:13 GMT</pubDate><dc:creator>Jerry Hung</dc:creator></item><item><title>8.3 filenames and FILESTREAM</title><link>http://www.sqlservercentral.com/Forums/Topic575303-538-1.aspx</link><description>I'm excited about the new FILESTREAM object, but it has a hidden flaw that must be discussed!  If you start loading 100,000+ files into a table, the performance for inserting rows will continue to slow down to the point where it is crawling (several seconds for a single insert!)This problem occurs because NTFS is continuing to create 8.3 file names for each file that is created in the FILESTREAM directory.This is not a SQL command, or configuration issue - but an NTFS known problem that was not addressed when SQL creates the directory.You can stop NTFS from creating 8.3 filesname, and therefore restore performance!Here is the command to be issued in the diretory: fsutil behavior set disable8dot3More information here: http://technet.microsoft.com/en-us/library/bb457112.aspx - scroll down to Optimizing NTFS Performance. - credit to channel9!</description><pubDate>Wed, 24 Sep 2008 09:11:56 GMT</pubDate><dc:creator>Richard Reukema</dc:creator></item></channel></rss>