Click here to monitor SSC
SQLServerCentral is supported by Redgate
Log in  ::  Register  ::  Not logged in
Home       Members    Calendar    Who's On

Add to briefcase ««12

FILESTREAM Data Expand / Collapse
Posted Wednesday, April 1, 2009 6:36 PM
Forum Newbie

Forum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum NewbieForum Newbie

Group: General Forum Members
Last Login: Thursday, April 1, 2010 2:00 PM
Points: 1, Visits: 4
I'm sorry I didn't see this question yesterday...

Back in 2003/4 I was one of the SDE/T's at Microsoft testing the new Filestreams feature in Yukon (2005). One of my responsibilities was to test the performance of the filesystem, to see what would happen when SQL server started generating large numbers of files in a directory. At the time, the Microsoft standard line was they did not recommend putting more than ~100,000 files in a single directory. I wrote programs that created, deleted, and did random seeks on directories with millions of files.

I was actually the guy who made the recommendation to suggest turning off 8.3 names, after my testing found that filesystem performance got exponentially worse after only a few hundred thousand files.

I remember the windows guys were shocked when I told them I wrote a program that generated over 20 million files in a single directory, with only slight linear performance degradation.

Ahh, the memories.
Post #688493
Posted Thursday, January 12, 2012 2:09 AM


Group: General Forum Members
Last Login: Monday, December 5, 2016 6:47 PM
Points: 2,587, Visits: 734
I disagree with author!

second answer it is recommendation for optimization ntfs perfomance.
in isn't necessary.

MS SQL 2008 MCITP x 3
MS SQL 2012 MCSE x 2
Post #1234576
« Prev Topic | Next Topic »

Add to briefcase ««12

Permissions Expand / Collapse