Identity range issue while subscribing

Please start any new threads on our new site at https://forums.sqlteam.com. We've got lots of great SQL Server experts to answer whatever question you can come up with.

All Forums

General SQL Server Forums

New to SQL Server Administration

Identity range issue while subscribing

Author

Topic

shobhaaradhya
Starting Member

37 Posts

Posted - 2012-11-08 : 05:48:00

Hi,

I am facing a serious issue with subscription. The scenario is

After restoring and making the changes to db 'Stationarytx'.

I am taking an example of a table "PaperPrint"

select max(id) from PaperPrint

results 1876100038

(Max id for the same table in before restoring is 1473000025.)

Now publish the db and create snapshot.

After publishing the identity range is setting correctly for this table ie ID > 1876100038 and ID < 1876000000.

Start subscribing the db.

After sql merge agent is executed successfully when I look into the subscribed database ie "PaperPrint" table the identity range will be ([ID] > 147500000 and [ID] < 147600000) and the identity range for the same table in publisher db is also ([ID] > 147400000 and [ID] < 147500000). So the identity range which is set while publishing is completely gone.

If again I republish db and subscribe the ranges would have increased by 1000000 ie (ofcourse this is the range set while publishing)

in publisher - [ID] > 147600000 and [ID] < 147700000

in subscribed db - [ID] > 147700000 and [ID] < 147800000

This is happening for all the tables which has identity key property.

I am creating only one subscription.

I get the following warning during publishing

Warning: only Subscribers running SQL Server 2000 can synchronize with publication 'xxx' because automatic identity ranges are being used.
Warning: only Subscribers running SQL Server 2000 can synchronize with publication 'xxx' because column-level collation is scripted out with the article schema creation script.
Warning: only Subscribers running SQL Server 2000 can synchronize with publication 'xxx' because extended properties are scripted out with the article schema creation script.
Warning: only Subscribers running SQL Server 2000 can synchronize with publication 'xxx' because data types new in SQL Server 2000 exist in one of its articles.

Any help would be appreciated. Pls.

Thanks,

Subscribe to SQLTeam.com

SQLTeam.com Articles via RSS

SQLTeam.com Weblog via RSS

- Advertisement -

Resources