BugZero found this defect 1308 days ago.
Data sources
All data on this page is proprietary to BugZero® or gathered from public sources
7/18/2023
SQL 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)
SQL Server 2014 Service Pack 2 - duplicate (do not use)
SQL Server 2014 Developer - duplicate (do not use)
SQL Server 2014 Enterprise - duplicate (do not use)
SQL Server 2014 Enterprise Core - duplicate (do not use)
SQL Server 2014 Standard - duplicate (do not use)
SQL Server 2017 on Windows (all editions)
build lower than 14.0.3045.24
14.0.3045.24
Assume that you enable the Change Data Capture (CDC) feature on a table to run a log scan in Microsoft SQL Server. The pollinginterval parameter is converted from seconds (s) to hours (h) in the sys.sp_cdc_scan stored procedure. However, when the pollinginterval parameter is greater than one hour (>3600 s), you notice that the converted result is incorrect. declare @pollinginterval bigint, @seconds bigint, @minutes bigint, @hours bigint set @pollinginterval = 3600 select @seconds = @pollinginterval % 60 select @minutes = ((@pollinginterval - @seconds) / 60) % 60 select @hours = (@pollinginterval - (@minutes * 60) - @seconds) / 60 --- Next attempt below line instead --- select @hours = (@pollinginterval - (@minutes * 60) - @seconds) / 60 /60 select @hours, @minutes, @seconds
This problem is fixed in the following cumulative updates for SQL Server: Cumulative Update 12 for SQL Server 2017 Cumulative Update 3 for SQL Server 2016 SP2 Cumulative Update 12 for SQL Server 2016 SP1 Cumulative Update 1 for SQL Server 2014 SP3 Cumulative Update 14 for SQL Server 2014 SP2