Great community. Great ideas.
Welcome to ASP/Free, a community dedicated to helping beginners and professionals alike in improving their knowledge of Microsoft's development and administration technologies. Sign up today to gain access to the combined insight of tens of thousands of members.
November 12th, 2012, 05:27 AM
Issue with identity range while subscribing
I am facing a serious issue with subscription. The scenario is
I am restoring a db and do some changes like adding/ updating/deleting few tables/SP/functions. the db name is 'Stationarytx'. Now
I am taking an example of a table "PaperPrint"
select max(id) from PaperPrint
(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.
How can I resolve this issue?
Thanks in advance
By RSS_News_User in forum Technology News
Last Post: September 15th, 2011, 09:00 AM
By dcorey in forum ASP Development
Last Post: June 24th, 2009, 03:32 PM
By stupadasil in forum ASP Development
Last Post: December 27th, 2006, 02:32 AM
By maxamis4 in forum Microsoft Access Help
Last Post: February 13th, 2006, 04:40 PM
By twopecker in forum Microsoft SQL Server
Last Post: July 5th, 2005, 09:59 AM