Note: Forums will be making significant UX changes to address key usability improvements surrounding search, discoverability and navigation. To learn more about these changes please visit the announcement which can be found HERE.
Identity range check conflict when inserting a table constructed value....

Unanswered Identity range check conflict when inserting a table constructed value....

  • 14 марта 2012 г. 12:16
     
     


    It seems to be the same problem as :

    Consider the following scenario. In SQL Server 2008, you configure a merge publication. You add a table that contains an identity column to the merge publication. Then, you try to perform a batch insert into the table on the publisher. In this scenario, you may receive the following error message on the publisher. 

    http://support.microsoft.com/kb/972006

    I'm actually using the a table constructed value of a few hundreds records...


    SQL Server 2008 introduces the Transact-SQL row constructor (also called a table value constructor) to specify multiple rows in a single INSERT statement. The row constructor consists of a single VALUES clause with multiple value lists enclosed in parentheses and separated by a comma. For more information, see Table Value Constructor (Transact-SQL).

    but I was wandering if there's any other option ? ...(or should I increase the range so that it could not be reached in a day and run the merge agent every night).

    How do you circumvent the problem in the real world :) ?

     

    thanks


Все ответы