Home Dashboard Directory Help
Search

Arithmetic Overflow in sp_MSarticle_validation by Brandon L


Status: 

Active


3
0
Sign in
to vote
Type: Bug
ID: 723133
Opened: 2/3/2012 10:46:25 AM
Access Restriction: Public
0
Workaround(s)
view
1
User(s) can reproduce this bug

Description

When attempting to call sp_article_validation on a replicated table with a row count of 10 billion rows or more, the following error is thrown:

Generated expected rowcount value of 11869637364 for <table name>
Msg 8115, Level 16, State 2, Procedure sp_MSarticle_validation, Line 231
Arithmetic overflow error converting expression to data type varchar.

Results for articles with over 10 billion rows are then not logged in MSdistribution_history.

It's been determined that sp_MSarticle_validation is converting @actual_rowcount (a bigint) to varchar(10) instead of varchar(19).
Details
Sign in to post a comment.
Posted by Microsoft on 6/28/2013 at 10:26 AM
Hi Brandon L,
    
as per my previous message I am archiving that discussion.

Best regards
Jean-Yves Devant
Senior Program Manager
Servicing of High Availability and Mobile Technologies in SQL Server.
Release management of SQL Server GDRs and Service Packs.
Posted by Microsoft on 6/28/2013 at 10:25 AM
Hi Brandon L,
    
Just to confirm we have checked in a fix in SQL Server 2014 branch. It should be available starting CTP2 of SQL Server 2014.

Best regards
Jean-Yves Devant
Senior Program Manager
Servicing of High Availability and Mobile Technologies in SQL Server.
Release management of SQL Server GDRs and Service Packs.
Posted by Microsoft on 11/12/2012 at 2:37 PM
Hi Brandon L,
    
This behavior is a defect which was not known till you shared it. We are planning to fix it in the next major release of SQL Server. Again, thanks for taking the time to share your feedback, this is really important to us.

Best regards
Jean-Yves Devant 
Program Manager Servicing and Lifecycle Experience of High Availability Technologies in SQL Server
Program Manager SQL Server Replication, Change Data Capture, Change Tracking
Posted by Microsoft on 2/21/2012 at 12:45 PM
Hi Brandon L ,
    
thanks for taking the time to share your feedback, this is really important to us.
We will investigate the issue and get back to you.

Best regards
Jean-Yves Devant
Program Manager (Replication/CDC/CT)
SQL Server Engine Team
Posted by Brandon Williams on 2/3/2012 at 10:58 AM
I was able reproduce this problem as well.
Sign in to post a workaround.