When to use Filestream partitions?

Question

We have a Web site where we do a lot of document management. We currently have a table with 370,000 records in it. When uploading a new file we check it's size and if it is below 2Gig we store it in a VarChar blob column. We currently want to alter that
table and add a Filestream column and transfer the data as shown below. As you see we are only creating one file folder and the query will probably run for six hours or so. 
We are also thinking about adding up to 5 million audio files stored in a different area. We could conceivably end up with several terabytes of file data. Should we partition and if so how many files should we store in each partition? We are using SQL Server
2012 and Windows Server 2012 R2.
--Create a ROWGUID column
USE CUR
ALTER Table documents
Add DocGUID uniqueidentifier not null ROWGUIDCOL unique default newid()
GO
--Turn on FILESTREAM
USE CUR
ALTER Table documents
SET (filestream_on=FileStreamGroup1)
GO
--Add FILESTREAM column to the table
USE CUR
ALTER Table documents
Add DocContent2 varbinary(max) FILESTREAM null
GO
-- Move data into the new column
UPDATE documents
SET DocContent2=DocContent
where doccontent is not null and  doccontent2 is null  
GO
--Drop the old column
ALTER Table documents
DROP column DocContent
GO
--Rename the new FILESTREAM column to the old column name
Use CUR
GO
 sp_rename 'documents.DocContent2', 'DocContent','Column'
GO

Answer 1

Hi tomheaser,
Quote: Should we partition and if so how many files should we store in each partition?
Yes, if our database contains very large tables, we may benefit from partitioning those tables onto separate filegroups. In this case, SQL Server can access all the drives of each partition at the same time, this may reduce a lot time to load data.
If you only want to reduce the query time by increasing the number of the filegroups, then the limit on the maximum number of partitions is 15,000 in SQL Server. But in order to maintain a balance between performance and number of partitions, we need to consider
more things such as memory, partitioned index operations, DBCC commands, and queries. So please consider all those things first, then choose a reasonable number of partitions. For more information about Performance Guidelines of Table Partition, please refer
to the following article:
http://msdn.microsoft.com/en-us/library/ms190787(v=sql.110).aspx
If you have any question, please feel free to let know.
Regards,
Jerry Li