When you query the SYS.DM_EXEC_QUERY_PROFILES DMV to examine an execution plan that references tables that contain many rows (more than 232), the DMV may return an incorrect number of rows in the “estimate_row_count” column of some operators, capping the value at 232.
Note Neither the estimated query plan or live query statistics are affected by this issue.
This issue occurs because the “estimate_row_count” column is internally handled as a 32-bit value. For values greater than 232, Microsoft SQL Server limits the column to 232.
This fix is included in Cumulative Update 2 for SQL Server 2017.
About SQL Server 2017 builds
Each new build of SQL Server 2017 contains all the hotfixes and security fixes that were in the previous build. We recommend that you install the latest build of SQL Server 2017.
Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
Learn about the terminology Microsoft uses to describe software updates.