Depends on usage. NTFS MFT is a hierarchical database, but which stores small files "inline" inside the database, and larger files as pointers to the actual location on disk. Then there is a completely separate issue of a client browsing to a shared folder (using Explorer) and expecting an enumeration of the contents.
So, for a server that just has lots of files on a drive - you can store a lot more files per folder (varies by size) than if it's a server hosting a shared folder that needs to be accessed by clients using SMB (other protocols, like HTTP or FTP would be different - the server being used and the properties exposed to the end client) Cheers Ken From: David Lum [mailto:[email protected]] Sent: Tuesday, 6 September 2011 11:46 PM To: NT System Admin Issues Subject: # of files on Windows server Recently we had a thread about how many files get to be too many for reasonable performance. Would this be just per folder, or possibly logical drive in general? Links/documents would work too. David Lum Systems Engineer // NWEATM Office 503.548.5229 // Cell (voice/text) 503.267.9764 ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to [email protected]<mailto:[email protected]> with the body: unsubscribe ntsysadmin ~ Finally, powerful endpoint security that ISN'T a resource hog! ~ ~ <http://www.sunbeltsoftware.com/Business/VIPRE-Enterprise/> ~ --- To manage subscriptions click here: http://lyris.sunbelt-software.com/read/my_forums/ or send an email to [email protected] with the body: unsubscribe ntsysadmin
