Viewing 6 posts - 1 through 7 (of 7 total)
cdooley - the DBCC CHECKIDENT RESEED resets the current identity from @range_end to @next_range_begin.
I would guess sys.sp_MSrefresh_publisher_idrange refreshes the actual ranges, though I haven't looked into how it does it.
I...
February 12, 2009 at 1:10 pm
I would guess that as a minimum, the subscriber needs to be able to browse to snapshot.pre, and download it.
Can it do this ?
You might find some clues in...
February 11, 2009 at 10:51 am
The way I understand it (and I may be wrong in places) is:
Subscribers running version 2005 and above no longer use a single range, and a percentage.
Instead they are allocated...
February 10, 2009 at 11:00 am
http://technet.microsoft.com/en-us/library/ms181527.aspx:
EXEC sp_adjustpublisheridentityrange @publication=publication_name
The above will adjust all tables in the publication publication_name where the current identity is outside the first range.
I assume the error was occuring when running an insert...
February 10, 2009 at 5:31 am
I've had ongoing discussions with Microsoft support, and progress has been made re the identity range management flaw.
The workaround they got back to me with was "There isn't one."
Then they...
February 9, 2009 at 4:38 am
According to http://msdn.microsoft.com/en-us/library/ms152543.aspx, the range threshold percentage is only used for subscribers running earlier versions of SQL Server, or SQL Server Compact 3.5SP1. So it's more of a backwards...
January 19, 2009 at 8:35 am
Viewing 6 posts - 1 through 7 (of 7 total)