Viewing 15 posts - 196 through 210 (of 353 total)
In 2K
The ranges are added automatically once you run the snapshot and merge agent. You can see these in the article properties. These can of course be changed if the...
October 16, 2007 at 9:04 am
The nickname is a number that is given automatically by merge replication to the articles. The PK/Parent tables have a higher number (I think that's the right way round) than...
October 16, 2007 at 8:47 am
Yes just to confirm
Merge replication manages it's own identities, and very well. It uses a stepped identity approach. Table A on Server A will have identity range of 1-1000, on...
October 16, 2007 at 5:39 am
Hi,
I think this related to the fact that if the child records are replicated before the parent, you will get key violations. Increasing the batch size may help to capture...
October 16, 2007 at 5:32 am
Hi,
If I remember correctly can you use sp_articleColumn
Regards
Graeme
October 16, 2007 at 5:27 am
Well it does, of course, depend on the reason for the replication in the first place. If this is for the purpose of DR then there are better ways of...
September 5, 2007 at 1:39 am
Just thought I would close this one as I have resolved the issue.
The large number being entered was actually the ID of the table from sysobjects.
This was because the Identity...
August 24, 2007 at 6:54 am
Hello John,
All the triggers are performing inserts only...it's like an audit log but just capturing specific changes.
If I perform a manual insert into the table, the Identity is created as...
August 23, 2007 at 9:10 am
Ok sure,
On the table DailyDataChanges the current identity is 1790309, so the next record that is entered by the triggers should have an Identity of 1790310....
But then as the triggers...
August 23, 2007 at 8:09 am
Hi,
Here is the table that is being populated from the trigger
CREATE TABLE [dbo].[tblDailyDataChanges] (
[DailyDataChangeID] [int] IDENTITY (1, 1) NOT FOR REPLICATION NOT NULL ,
[UniqueID] [int] NOT NULL ,
[DataEntityTypeID]...
August 23, 2007 at 5:30 am
Well that procedure is certainly an replication update procedure.
How big is tbl_Ev.
Is it being accessed all the time ?
What is its function?
Graeme
June 29, 2007 at 12:47 am
Hi,
Has quite a bit to do with the type of replication. We have user replication running on our live production website..this transactional repliaction.
Also what sort of tasks are the users...
June 28, 2007 at 1:46 am
Hi,
Just an extra note. We have a similar scenario. We are merge replicating between two databases that are both updated. One is then transactionally replicated to a third database for...
June 22, 2007 at 4:50 am
Hi,
You certainly can do that. When you apply replication (tran or Merge) you have the option to perform a no-sync subscription. In other words the subscriber is already in sync...
June 21, 2007 at 5:19 am
Hi,
I've used this (bit messy but works), any good
Graeme
SET NOCOUNT ON
/*Declare Variables*/
DECLARE @TabName varchar(50),@str varchar(8000),@Select varchar(8000),@colName Varchar(30), @Ord int,@Debug int
SET @Debug = 1
/*Set Cursor for table names*/
DECLARE tab_cursor CURSOR FOR...
June 21, 2007 at 5:01 am
Viewing 15 posts - 196 through 210 (of 353 total)