Symptoms
Consider the following scenario:
-
You have a FileTable or FILESTREAM in Microsoft SQL Server 2012 or SQL Server 2014.
-
You have set the MAXSIZE of FILESTREAM data to UNLIMITED.
-
You insert a record into the FileTable when the FILESTREAM container size has reached 32 terabytes (TB).
In this scenario, the insert fails and you receive the following error:
error 1105 Could not allocate space for object '<object_name>' in database '<database >’ because the '<filestream_filegroup>' filegroup is full.
Resolution
The issue was first fixed in the following cumulative update of SQL Server. After you apply the fix, when the FILESTREAM container MAXSIZE is set to UNLIMITED, it continues to grow until the disk is full.
Cumulative Update 2 for SQL Server 2012 SP2 /en-us/help/2983175
Cumulative Update 3 for SQL Server 2014 /en-us/help/2984923
Cumulative Update 11 for SQL Server 2012 SP1 /en-us/help/2975396
Each new cumulative update for SQL Server contains all the hotfixes and all the security fixes that were included with the previous cumulative update. Check out the latest cumulative updates for SQL Server:
Status
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
