Applies ToSQL Server 2016 Developer - duplicate (do not use) SQL Server 2016 Enterprise - duplicate (do not use) SQL Server 2016 Enterprise Core - duplicate (do not use) SQL Server 2016 Standard - duplicate (do not use)

Symptoms

Assume that you set the AUTOGROW_ALL_FILES property to a filegroup for a database in Microsoft SQL Server 2016, and the filegroup doesn't have the property set. In this situation, you receive the following error message:

Msg 5045, Level 16, State 3, Line 1The filegroup already has the 'AUTOGROW_ALL_FILES' property set.

Another issue is that when you set the AUTOGROW_ALL_FILES or READ_ONLY property to a filegroup, the property isn't preserved after the database or the server restarts. The sys.filegroups viewstill shows that the corresponding column for the property (is_autogrow_all_files and is_read_only) is set to 1. However, it's not actually effective.

Resolution

The issue was first fixed in the following cumulative update of SQL Server:

After you apply the fix, you should set the corresponding property again to make it effective. 

Each new cumulative update for SQL Server contains all the hotfixes and all the security fixes that were included with the previous cumulative update. We recommend that you download and install 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.

References

Learn about the terminology that Microsoft uses to describe software updates.See more information about ALTER DATABASE File and Filegroup Options.

Need more help?

Want more options?

Explore subscription benefits, browse training courses, learn how to secure your device, and more.

Communities help you ask and answer questions, give feedback, and hear from experts with rich knowledge.