FIX: "The integer value is out of range" error when you pass a bigint value as the last_sync_version argument of the CHANGETABLE function in SQL Server 2008 or in SQL Server 2008 R2

Article ID: 2519358 - View products that this article applies to.
Microsoft distributes Microsoft SQL Server 2008 Service Pack 1 (SP1) and Microsoft SQL Server 2008 R2 fixes as one downloadable file. Because the fixes are cumulative, each new release contains all the hotfixes and all the security fixes that were included with the previous SQL Server 2008 SP1 and SOL Server 2008 R2 fix release.
Expand all | Collapse all

On This Page

SYMPTOMS

Consider the following scenario:
  • You enable change tracking on a table in SQL Server 2008 or in SQL Server 2008 R2.
  • You run a query that uses the CHANGETABLE function together with the last_sync_version argument to return tracking information for the changes that occurred in the table.
  • A bigint value is passed as the last_sync_version argument.
For example, you run the following query after you enable change tracking on a table: 
SELECT * FROM CHANGETABLE(changes dbo.t1, 2222222222) as ct
In this scenario, the execution of the query fails and you receive the following information:
Msg 1080, Level 15, State 1, Line 1
The integer value the bigint value is out of range.
Notes
  • The type of the last_sync_version argument is defined as bigint. Therefore, the query is expected to run successfully.
  • the bigint value is a placeholder that represents the bigint value that is passed as the last_sync_version argument.
Back to the top | Give Feedback

RESOLUTION

Cumulative update information

SQL Server 2008 R2 Service Pack 1

The fix for this issue was first released in Cumulative Update 1 for SQL Server 2008 R2 Service Pack 1. For more information about how to obtain this cumulative update package, click the following article number to view the article in the Microsoft Knowledge Base:
2544793
(http://support.microsoft.com/kb/2544793/ )
Cumulative Update package 1 for SQL Server 2008 R2 Service Pack 1
Note Because the builds are cumulative, each new fix release contains all the hotfixes and all the security fixes that were included with the previous SQL Server 2008 R2 fix release. We recommend that you consider applying the most recent fix release that contains this hotfix. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
2567616
(http://support.microsoft.com/kb/2567616/ )
The SQL Server 2008 R2 builds that were released after SQL Server 2008 R2 Service Pack 1 was released

SQL Server 2008 Service Pack 2

The fix for this issue was first released in Cumulative Update 4 for SQL Server 2008 Service Pack 2. For more information about this cumulative update package, click the following article number to view the article in the Microsoft Knowledge Base:
2527180
(http://support.microsoft.com/kb/2527180/LN/ )
Cumulative update package 4 for SQL Server 2008 Service Pack 2
Note Because the builds are cumulative, each new fix release contains all the hotfixes and all the security fixes that were included with the previous SQL Server 2008 fix release. Microsoft recommends that you consider applying the most recent fix release that contains this hotfix. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
2402659
(http://support.microsoft.com/kb/2402659/LN/ )
The SQL Server 2008 builds that were released after SQL Server 2008 Service Pack 2 was released
Microsoft SQL Server 2008 hotfixes are created for specific SQL Server service packs. You must apply a SQL Server 2008 Service Pack 2 hotfix to an installation of SQL Server 2008 Service Pack 2. By default, any hotfix that is provided in a SQL Server service pack is included in the next SQL Server service pack.

SQL Server 2008 R2

The fix for this issue was first released in Cumulative Update 7. For more information about how to obtain this cumulative update package for SQL Server 2008 R2, click the following article number to view the article in the Microsoft Knowledge Base:
2507770
(http://support.microsoft.com/kb/2507770/ )
Cumulative Update package 7 for SQL Server 2008 R2
Note Because the builds are cumulative, each new fix release contains all the hotfixes and all the security fixes that were included with the previous SQL Server 2008 R2 fix release. We recommend that you consider applying the most recent fix release that contains this hotfix. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
981356
(http://support.microsoft.com/kb/981356/ )
The SQL Server 2008 R2 builds that were released after SQL Server 2008 R2 was released

The fix for this issue was first released in Cumulative Update 13. For more information about how to obtain this cumulative update package for SQL Server 2008 SP1, click the following article number to view the article in the Microsoft Knowledge Base:
2497673
(http://support.microsoft.com/kb/2497673/ )
Cumulative update package 13 for SQL Server 2008 Service Pack 1
Note Because the builds are cumulative, each new fix release contains all the hotfixes and all the security fixes that were included with the previous SQL Server 2008 SP1 fix release. We recommend that you consider applying the most recent fix release that contains this hotfix. For more information, click the following article number to view the article in the Microsoft Knowledge Base:
970365
(http://support.microsoft.com/kb/970365/ )
The SQL Server 2008 builds that were released after SQL Server 2008 Service Pack 1 was released
Back to the top | Give Feedback

STATUS

Microsoft has confirmed that this is a problem in the Microsoft products that are listed in the "Applies to" section.
Back to the top | Give Feedback

WORKAROUND

To work around this issue, create a variable of type bigint, and then pass the variable as the last_sync_version argument of the CHANGETABLE function. For example, you can successfully run the following query: 
DECLARE @v3 bigint = 2222222222
SELECT * FROM CHANGETABLE(changes dbo.t1, @v3 ) as ct
Back to the top | Give Feedback

MORE INFORMATION

For more information about the CHANGETABLE function for Transact-SQL, visit the following Microsoft Development Network (MSDN) website:
General information about the CHANGETABLE function for Transact-SQL
(http://msdn.microsoft.com/en-us/library/bb934145(v=SQL.100).aspx)
Back to the top | Give Feedback

Properties

Article ID: 2519358 - Last Review: July 19, 2011 - Revision: 4.1
APPLIES TO
  • Microsoft SQL Server 2008 Developer
  • Microsoft SQL Server 2008 Enterprise
  • Microsoft SQL Server 2008 Enterprise Evaluation
  • Microsoft SQL Server 2008 Express
  • Microsoft SQL Server 2008 Service Pack 2
  • Microsoft SQL Server 2008 R2 Developer
  • Microsoft SQL Server 2008 R2 Enterprise
  • Microsoft SQL Server 2008 R2 Express
Keywords: 
kbqfe kbfix kbexpertiseadvanced kbsurveynew KB2519358
Back to the top | Give Feedback

Give Feedback

 
Back to the topBack to the top