replication conflicts for 2 tables

Hi,
we are using merge replication between remote sites and
our central office. couple months ago we had a situation
where we had to insert some records and update other
records with these inserted records and then delete the
inserted records. Then we reinserted these records again
without replicating the deletes to our remote sites.
by doing this we had lots of conflicts.
I mannually deleted replicated and reinserted the records
again.
all other sites are fine but 2 of our sites, which were
disconnected during the delete replication did not get the
deleted records and they still shows conflicts every day
when they replicate. even though these records are not
being edited at all. For some reason they get marked for
replication and shows up in conflicts.
we don't care if those changes doesn't get replicated to
the remote sites becos they don't need those changes. how
do I stop them to show up in conflicts.
thanks
Kiran
did you resolve these conflicts using the conflict viewer? This is the
preferred way of solving this problem?
"Kiran" <anonymous@.discussions.microsoft.com> wrote in message
news:16bc201c41752$0defc130$a101280a@.phx.gbl...
> Hi,
> we are using merge replication between remote sites and
> our central office. couple months ago we had a situation
> where we had to insert some records and update other
> records with these inserted records and then delete the
> inserted records. Then we reinserted these records again
> without replicating the deletes to our remote sites.
> by doing this we had lots of conflicts.
> I mannually deleted replicated and reinserted the records
> again.
> all other sites are fine but 2 of our sites, which were
> disconnected during the delete replication did not get the
> deleted records and they still shows conflicts every day
> when they replicate. even though these records are not
> being edited at all. For some reason they get marked for
> replication and shows up in conflicts.
> we don't care if those changes doesn't get replicated to
> the remote sites becos they don't need those changes. how
> do I stop them to show up in conflicts.
> thanks
> Kiran
sql

Replication Chain Problem

Is it possible to setup a merge replication chain where you have a Head
Office (HO) which is a publisher to a Region Office (RO) subscriber which is
a publisher to a Store Office (SO) subscriber where the data travels both
directions fully? eg. HO<->RO<->SO.
From testing, it appears that if data is changed at the SO, then it only
gets merged to the RO, not the HO as well.
Do anyone know what needs to be done to get it also merged to the HO as well?
this should work. As long as all the downstream subscribers have a lower
priority than the upstream publisher/subscriber the data should move as you
desire. You might want to check to make sure that the missing data isn't
logged in the conflict tables.
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"Cheval" <Cheval@.discussions.microsoft.com> wrote in message
news:8D8A9DE5-B207-4CF2-997C-5BD65A3EDD01@.microsoft.com...
> Is it possible to setup a merge replication chain where you have a Head
> Office (HO) which is a publisher to a Region Office (RO) subscriber which
> is
> a publisher to a Store Office (SO) subscriber where the data travels both
> directions fully? eg. HO<->RO<->SO.
> From testing, it appears that if data is changed at the SO, then it only
> gets merged to the RO, not the HO as well.
> Do anyone know what needs to be done to get it also merged to the HO as
> well?
|||No issues. I've built these as deep as 16 levels with data flowing in both
directions.
Mike
http://www.solidqualitylearning.com
Disclaimer: This communication is an original work and represents my sole
views on the subject. It does not represent the views of any other person
or entity either by inference or direct reference.
"Cheval" <Cheval@.discussions.microsoft.com> wrote in message
news:8D8A9DE5-B207-4CF2-997C-5BD65A3EDD01@.microsoft.com...
> Is it possible to setup a merge replication chain where you have a Head
> Office (HO) which is a publisher to a Region Office (RO) subscriber which
> is
> a publisher to a Store Office (SO) subscriber where the data travels both
> directions fully? eg. HO<->RO<->SO.
> From testing, it appears that if data is changed at the SO, then it only
> gets merged to the RO, not the HO as well.
> Do anyone know what needs to be done to get it also merged to the HO as
> well?

Replication between SQL server and SQL express ??

Dear all,
I try to setup a replication between a database TEST on a server myServer
into an SQL express database myDB on a Vista office PC machine.
For that I define my SQL server to be a publisher of my database TEST and
then on my Client PC under sqL express I define a new subscription by
selection my SQL server as the publisher. Setup goes fine until it try the
firts initialisation with the only mesage initialisation failed..
What do I have to verify ?
If on my SQL server dtabase I want to publish table EVENT, does that table
need to be already created in my SQL express before initialisation or it will
created automaticaly ?
Which permission type should be use from both side... ? for time beeing I
was using 'sa'
thnaks for help
rergards
serge
Replication will create the table for you. There is no need for you to
pre-create it. Can you enable logging so we can see where replication is
failing.
Use this link to enable it.
http://support.microsoft.com/kb/312292
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"calderara" <calderara@.discussions.microsoft.com> wrote in message
news:AEDF7E8F-8D58-488E-A3B0-DDCD38575CCF@.microsoft.com...
> Dear all,
> I try to setup a replication between a database TEST on a server myServer
> into an SQL express database myDB on a Vista office PC machine.
> For that I define my SQL server to be a publisher of my database TEST and
> then on my Client PC under sqL express I define a new subscription by
> selection my SQL server as the publisher. Setup goes fine until it try the
> firts initialisation with the only mesage initialisation failed..
> What do I have to verify ?
> If on my SQL server dtabase I want to publish table EVENT, does that table
> need to be already created in my SQL express before initialisation or it
> will
> created automaticaly ?
> Which permission type should be use from both side... ? for time beeing I
> was using 'sa'
> thnaks for help
> rergards
> serge
|||OK I will try to setup thge login...
Just for you to know that I have use the snaphot method for replication and
when I use the replication monitor and press th re iintialize menu...it goes
from status running to status fail retry initializing after a while and of
course my table is not created on my client machine.
Any rigths to verify on my client machine under EXPRES 2005 for the
receiving database ?
regards
"Hilary Cotter" wrote:

> Replication will create the table for you. There is no need for you to
> pre-create it. Can you enable logging so we can see where replication is
> failing.
> Use this link to enable it.
> http://support.microsoft.com/kb/312292
> --
> Hilary Cotter
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
> Looking for a FAQ on Indexing Services/SQL FTS
> http://www.indexserverfaq.com
>
> "calderara" <calderara@.discussions.microsoft.com> wrote in message
> news:AEDF7E8F-8D58-488E-A3B0-DDCD38575CCF@.microsoft.com...
>
>
|||I have generated the log file.
I can paste the whol content here ?
What I have noticed if I read properly is that the sanphot seems to work ok
as when starting the agent I get status complete succesfully.I think the
problem come from the time it needs to copy the snapshot to the Client SQL
express 2005 database...
:-(
"Hilary Cotter" wrote:

> Replication will create the table for you. There is no need for you to
> pre-create it. Can you enable logging so we can see where replication is
> failing.
> Use this link to enable it.
> http://support.microsoft.com/kb/312292
> --
> Hilary Cotter
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
> Looking for a FAQ on Indexing Services/SQL FTS
> http://www.indexserverfaq.com
>
> "calderara" <calderara@.discussions.microsoft.com> wrote in message
> news:AEDF7E8F-8D58-488E-A3B0-DDCD38575CCF@.microsoft.com...
>
>
|||Yes, please post the whole thing here. It sounds like you might have done
this for the snapshot agent. You may need to do this for the
merge/distribution agent as well.
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"calderara" <calderara@.discussions.microsoft.com> wrote in message
news:3243F73C-43DF-458A-837D-615F57DF16D4@.microsoft.com...[vbcol=seagreen]
>I have generated the log file.
> I can paste the whol content here ?
> What I have noticed if I read properly is that the sanphot seems to work
> ok
> as when starting the agent I get status complete succesfully.I think the
> problem come from the time it needs to copy the snapshot to the Client SQL
> express 2005 database...
> :-(
>
> "Hilary Cotter" wrote:
|||Thanks for your prompt reply..
Where can I find the merge/replication agent ? in my list where I have doen
previous steps I have seen only the snapshot agent ?
regards
serge
"Hilary Cotter" wrote:

> Yes, please post the whole thing here. It sounds like you might have done
> this for the snapshot agent. You may need to do this for the
> merge/distribution agent as well.
> --
> Hilary Cotter
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
> Looking for a FAQ on Indexing Services/SQL FTS
> http://www.indexserverfaq.com
>
> "calderara" <calderara@.discussions.microsoft.com> wrote in message
> news:3243F73C-43DF-458A-837D-615F57DF16D4@.microsoft.com...
>
>
|||Hi hilary,
Here is below the file output requested for the type : "Replication
snapshot" part 1
================================================
2007-03-21 14:42:57.75
2007-03-21 14:42:57.75 Microsoft (R) SQL Server Snapshot Agent
2007-03-21 14:42:57.75 [Assembly Version = 9.0.242.0, File Version =
9.00.1399.00]
2007-03-21 14:42:57.75 Copyright (C) 1988-2005 Microsoft Corporation. All
rights reserved.
2007-03-21 14:42:57.75 The timestamps prepended to the output lines are
expressed in terms of UTC time.
2007-03-21 14:42:57.75 User-specified agent parameter values:
2007-03-21 14:42:57.75 ---
2007-03-21 14:42:57.75 -Publisher NOMOS-SRVR
2007-03-21 14:42:57.75 -PublisherDB TEST
2007-03-21 14:42:57.75 -Publication TestPublication
2007-03-21 14:42:57.75 -Distributor NOMOS-SRVR
2007-03-21 14:42:57.75 -DistributorSecurityMode 1
2007-03-21 14:42:57.75 -Output d:\output.txt
2007-03-21 14:42:57.75 -OutputVerboseLevel 2
2007-03-21 14:42:57.75 -XJOBID 0x88F5D8DDCAC5174B953F14E7691E823B
2007-03-21 14:42:57.75 ---
2007-03-21 14:42:57.75 Connecting to Distributor 'NOMOS-SRVR'
2007-03-21 14:42:57.96
2007-03-21 14:42:57.96 SQL Command dump
2007-03-21 14:42:57.96 ================
2007-03-21 14:42:57.96 Server: NOMOS-SRVR
2007-03-21 14:42:57.96 Database: master
2007-03-21 14:42:57.96 Command Text: sp_helpdistpublisher
2007-03-21 14:42:57.96 Parameters:
2007-03-21 14:42:57.96 @.publisher = NOMOS-SRVR
2007-03-21 14:42:57.96
2007-03-21 14:42:57.96 SQL Command dump
2007-03-21 14:42:57.96 ================
2007-03-21 14:42:57.96 Server: NOMOS-SRVR
2007-03-21 14:42:57.96 Database: distribution
2007-03-21 14:42:57.96 Command Text: select 'id' = convert(int, srvid) from
master..sysservers where upper(srvname) = upper(N'NOMOS-SRVR')
2007-03-21 14:42:57.96 Parameters:
2007-03-21 14:42:57.96
2007-03-21 14:42:57.96 SQL Command dump
2007-03-21 14:42:57.96 ================
2007-03-21 14:42:57.96 Server: NOMOS-SRVR
2007-03-21 14:42:57.96 Database: distribution
2007-03-21 14:42:57.96 Command Text: sp_MShelp_snapshot_agentid
2007-03-21 14:42:57.96 Parameters:
2007-03-21 14:42:57.96 @.publisher_id = 0
2007-03-21 14:42:57.96 @.publisher_db = TEST
2007-03-21 14:42:57.96 @.publication = TestPublication
2007-03-21 14:42:57.96 @.job_id = System.Byte[]
2007-03-21 14:42:57.96
2007-03-21 14:42:57.96 SQL Command dump
2007-03-21 14:42:57.96 ================
2007-03-21 14:42:57.96 Server: NOMOS-SRVR
2007-03-21 14:42:57.96 Database: distribution
2007-03-21 14:42:57.96 Command Text: sp_MShelp_snapshot_agent
2007-03-21 14:42:57.96 Parameters:
2007-03-21 14:42:57.96 @.agent_id = 1
2007-03-21 14:42:57.98
2007-03-21 14:42:57.98 SQL Command dump
2007-03-21 14:42:57.98 ================
2007-03-21 14:42:57.98 Server: NOMOS-SRVR
2007-03-21 14:42:57.98 Database: distribution
2007-03-21 14:42:57.98 Command Text: sp_MShelp_profile
2007-03-21 14:42:57.98 Parameters:
2007-03-21 14:42:57.98 @.agent_id = 1
2007-03-21 14:42:57.98 @.agent_type = 1
2007-03-21 14:42:57.98 @.profile_name =
2007-03-21 14:42:57.98 Parameter values obtained from agent profile:
2007-03-21 14:42:57.98 ---
2007-03-21 14:42:57.98 -BcpBatchSize 100000
2007-03-21 14:42:57.98 -HistoryVerboseLevel 2
2007-03-21 14:42:57.98 -LoginTimeout 15
2007-03-21 14:42:57.98 -QueryTimeout 1800
2007-03-21 14:42:57.98 ---
2007-03-21 14:42:58.00 Connecting to Publisher 'NOMOS-SRVR'
2007-03-21 14:42:58.03
2007-03-21 14:42:58.03 SQL Command dump
2007-03-21 14:42:58.03 ================
2007-03-21 14:42:58.03 Server: NOMOS-SRVR
2007-03-21 14:42:58.03 Database: TEST
2007-03-21 14:42:58.03 Command Text: use master
2007-03-21 14:42:58.03 select isnull(convert(int, value_in_use), 0) from
master.sys.configurations where lower(name) = 'smo and dmo xps'
2007-03-21 14:42:58.03 use [TEST]
2007-03-21 14:42:58.03 Parameters:
2007-03-21 14:42:58.04
2007-03-21 14:42:58.04 SQL Command dump
2007-03-21 14:42:58.04 ================
2007-03-21 14:42:58.04 Server: NOMOS-SRVR
2007-03-21 14:42:58.04 Database: TEST
2007-03-21 14:42:58.04 Command Text: use [TEST]
2007-03-21 14:42:58.04 select publishingservername(), convert(int,
compatibility_level) from sys.databases where name = @.database_name
2007-03-21 14:42:58.04 Parameters:
2007-03-21 14:42:58.04 @.database_name = TEST
2007-03-21 14:42:58.04 Publisher database compatibility level is set to 80.
2007-03-21 14:42:58.04
2007-03-21 14:42:58.04 SQL Command dump
2007-03-21 14:42:58.04 ================
2007-03-21 14:42:58.04 Server: NOMOS-SRVR
2007-03-21 14:42:58.04 Database: TEST
2007-03-21 14:42:58.04 Command Text: select convert(int,
isnull(is_member('db_owner'),0))
2007-03-21 14:42:58.04 Parameters:
2007-03-21 14:42:58.04
2007-03-21 14:42:58.04 SQL Command dump
2007-03-21 14:42:58.04 ================
2007-03-21 14:42:58.04 Server: NOMOS-SRVR
2007-03-21 14:42:58.04 Database: TEST
2007-03-21 14:42:58.04 Command Text:
2007-03-21 14:42:58.04 declare @.retcode int
2007-03-21 14:42:58.04 exec @.retcode = sys.sp_getapplock @.Resource =
N'NOMOS-SRVR-TEST-TestPublication-1',
2007-03-21 14:42:58.04 @.LockMode =
N'Exclusive',
2007-03-21 14:42:58.04 @.LockOwner =
N'Session',
2007-03-21 14:42:58.04 @.LockTimeout = 0,
2007-03-21 14:42:58.04 @.DbPrincipal =
N'db_owner'
2007-03-21 14:42:58.04 if @.retcode < 0 raiserror(21036, 16, -1, 'snapshot')
2007-03-21 14:42:58.04 Parameters:
2007-03-21 14:42:58.04 Retrieving publication and article information from
the publisher database 'NOMOS-SRVR.TEST'
2007-03-21 14:42:58.04
2007-03-21 14:42:58.04 SQL Command dump
2007-03-21 14:42:58.04 ================
2007-03-21 14:42:58.04 Server: NOMOS-SRVR
2007-03-21 14:42:58.04 Database: TEST
2007-03-21 14:42:58.04 Command Text: sp_helppublication
2007-03-21 14:42:58.04 Parameters:
2007-03-21 14:42:58.04 @.publication = TestPublication
2007-03-21 14:42:58.04
2007-03-21 14:42:58.04 SQL Command dump
2007-03-21 14:42:58.04 ================
2007-03-21 14:42:58.04 Server: NOMOS-SRVR
2007-03-21 14:42:58.04 Database: TEST
2007-03-21 14:42:58.04 Command Text: if
object_id('sys.sp_checkinvalidivarticle') < 0 exec sp_checkinvalidivarticle
@.mode, @.publication
2007-03-21 14:42:58.04 Parameters:
2007-03-21 14:42:58.04 @.mode = 1
2007-03-21 14:42:58.04 @.publication = TestPublication
2007-03-21 14:42:58.04
2007-03-21 14:42:58.04 SQL Command dump
2007-03-21 14:42:58.04 ================
2007-03-21 14:42:58.04 Server: NOMOS-SRVR
2007-03-21 14:42:58.04 Database: TEST
2007-03-21 14:42:58.04 Command Text: declare @.ftp_password nvarchar(524)
select @.ftp_password = ftp_password from dbo.syspublications where name =
N'TestPublication' if object_id('sys.fn_repldecryptver4', 'FN') is not null
begin select sys.fn_repldecryptver4(@.ftp_password) end else begin select
@.ftp_password end
2007-03-21 14:42:58.04 Parameters:
2007-03-21 14:42:58.04
2007-03-21 14:42:58.04 SQL Command dump
2007-03-21 14:42:58.04 ================
2007-03-21 14:42:58.04 Server: NOMOS-SRVR
2007-03-21 14:42:58.04 Database: TEST
2007-03-21 14:42:58.04 Command Text: SET TRANSACTION ISOLATION LEVEL READ
COMMITTED;BEGIN TRANSACTION
2007-03-21 14:42:58.04 Parameters:
2007-03-21 14:42:58.04
2007-03-21 14:42:58.04 SQL Command dump
2007-03-21 14:42:58.04 ================
2007-03-21 14:42:58.04 Server: NOMOS-SRVR
2007-03-21 14:42:58.04 Database: TEST
2007-03-21 14:42:58.04 Command Text: sp_MSestimatesnapshotworkload
2007-03-21 14:42:58.04 Parameters:
2007-03-21 14:42:58.04 @.publication = TestPublication
2007-03-21 14:42:58.06
2007-03-21 14:42:58.06 SQL Command dump
2007-03-21 14:42:58.06 ================
2007-03-21 14:42:58.06 Server: NOMOS-SRVR
2007-03-21 14:42:58.06 Database: TEST
2007-03-21 14:42:58.06 Command Text: COMMIT TRANSACTION
2007-03-21 14:42:58.06 Parameters:
2007-03-21 14:42:58.06
2007-03-21 14:42:58.06 SQL Command dump
2007-03-21 14:42:58.06 ================
2007-03-21 14:42:58.06 Server: NOMOS-SRVR
2007-03-21 14:42:58.06 Database: TEST
2007-03-21 14:42:58.06 Command Text: SET TRANSACTION ISOLATION LEVEL READ
COMMITTED;BEGIN TRANSACTION
2007-03-21 14:42:58.06 Parameters:
2007-03-21 14:42:58.06
2007-03-21 14:42:58.06 SQL Command dump
2007-03-21 14:42:58.06 ================
2007-03-21 14:42:58.06 Server: NOMOS-SRVR
2007-03-21 14:42:58.06 Database: TEST
2007-03-21 14:42:58.06 Command Text: exec sys.sp_getapplock @.Resource =
@.publication, @.LockMode = N'Shared', @.LockOwner = N'Session', @.DbPrincipal =
N'db_owner'
2007-03-21 14:42:58.06 select 'article id' = art.artid,
2007-03-21 14:42:58.06 'article name' = art.name,
2007-03-21 14:42:58.06 'base object' = null,
2007-03-21 14:42:58.06 'destination_object' =
art.dest_table,
2007-03-21 14:42:58.06 'synchronization object' =
object_name(art.sync_objid),
2007-03-21 14:42:58.06 'type' = case when
objectproperty(art.objid, 'IsSchemaBound') = 1 and art.type <> 0x80 then
0x0100 | convert(smallint, art.type) else art.type end,
2007-03-21 14:42:58.06 'status' = art.status,
2007-03-21 14:42:58.06 'filter' = null,
2007-03-21 14:42:58.06 'description' = null,
2007-03-21 14:42:58.06 'insert_command' = art.ins_cmd,
2007-03-21 14:42:58.06 'update_command' = art.upd_cmd,
2007-03-21 14:42:58.06 'delete_command' = art.del_cmd,
2007-03-21 14:42:58.06 'creation script path' =
art.creation_script,
2007-03-21 14:42:58.06 'vertical partition' =
convert(bit, case when (art.type & 1) <> 1 or
2007-03-21 14:42:58.06
not exists (select *
2007-03-21 14:42:58.06
from sys.columns cols
2007-03-21 14:42:58.06
where cols.object_id = art.objid
2007-03-21 14:42:58.06
and not ((art.status & 32)=32 and
cols.system_type_id = 189)
2007-03-21 14:42:58.06
and cols.column_id not in (select artcols.colid
2007-03-21 14:42:58.06
from
dbo.sysarticlecolumns artcols
2007-03-21 14:42:58.06
where artcols.artid =
art.artid)) then 0
2007-03-21 14:42:58.06 else 1 end),
2007-03-21 14:42:58.06 'pre_creation_cmd' =
art.pre_creation_cmd,
2007-03-21 14:42:58.06 'filter_clause' =
art.filter_clause,
2007-03-21 14:42:58.06 'schema_option' =
art.schema_option,
2007-03-21 14:42:58.06 'dest_owner' =
art.dest_owner,
2007-03-21 14:42:58.06 'source_owner' =
schema_name(convert(int, objectpropertyex(art.objid, 'SchemaId'))),
2007-03-21 14:42:58.06 'unqua_source_object' =
object_name(art.objid),
2007-03-21 14:42:58.06 'sync_object_owner' =
schema_name(convert(int, objectpropertyex(art.sync_objid, 'SchemaId'))),
2007-03-21 14:42:58.06 'unqualified_sync_object' =
object_name(art.sync_objid),
2007-03-21 14:42:58.06 'filter_owner' = null,
2007-03-21 14:42:58.06 'unqua_filter' = null,
2007-03-21 14:42:58.06 'auto_identity_range' = null,
2007-03-21 14:42:58.06 'publisher_identity_range' = null,
2007-03-21 14:42:58.06 'identity_range' = null,
2007-03-21 14:42:58.06 'threshold' = null,
2007-03-21 14:42:58.06 'identityrangemanagementoption' = null,
2007-03-21 14:42:58.06 'fire_triggers_on_snapshot' =
convert(bit, art.fire_triggers_on_snapshot)
2007-03-21 14:42:58.06 from dbo.sysextendedarticlesview art
2007-03-21 14:42:58.06 inner join dbo.syspublications pub
2007-03-21 14:42:58.06 on art.pubid = pub.pubid
2007-03-21 14:42:58.06 where pub.name = @.publication
2007-03-21 14:42:58.06 Parameters:
2007-03-21 14:42:58.06 @.publication = TestPublication
2007-03-21 14:42:58.06
2007-03-21 14:42:58.06 SQL Command dump
2007-03-21 14:42:58.06 ================
2007-03-21 14:42:58.06 Server: NOMOS-SRVR
2007-03-21 14:42:58.06 Database: TEST
2007-03-21 14:42:58.06 Command Text: COMMIT TRANSACTION
2007-03-21 14:42:58.06 Parameters:
2007-03-21 14:42:58.07
2007-03-21 14:42:58.07 SQL Command dump
2007-03-21 14:42:58.07 ================
2007-03-21 14:42:58.07 Server: NOMOS-SRVR
2007-03-21 14:42:58.07 Database: TEST
2007-03-21 14:42:58.07 Command Text: sys.sp_MSget_load_hint
2007-03-21 14:42:58.07 Parameters:
2007-03-21 14:42:58.07 @.qualified_source_object_name = [dbo].[STATE]
2007-03-21 14:42:58.07 @.qualified_sync_object_name =
[dbo].[syncobj_0x3737313837413543]
2007-03-21 14:42:58.07 @.primary_key_only = False
2007-03-21 14:42:58.07 @.is_vertically_partitioned = False
2007-03-21 14:42:58.07
2007-03-21 14:42:58.07 SQL Command dump
2007-03-21 14:42:58.07 ================
2007-03-21 14:42:58.07 Server: NOMOS-SRVR
2007-03-21 14:42:58.07 Database: TEST
2007-03-21 14:42:58.07 Command Text:
2007-03-21 14:42:58.07 set nocount on
2007-03-21 14:42:58.07 declare @.source_object_id int
2007-03-21 14:42:58.07 declare @.sync_object_id int
2007-03-21 14:42:58.07
2007-03-21 14:42:58.07 set @.source_object_id =
object_id(quotename(@.source_object_schema) + N'.' +
quotename(@.source_object_name))
2007-03-21 14:42:58.07 set @.sync_object_id =
object_id(quotename(@.sync_object_schema) + N'.' +
quotename(@.sync_object_name))
2007-03-21 14:42:58.07
2007-03-21 14:42:58.07 declare @.partitioning_column sysname
2007-03-21 14:42:58.07 declare @.partitioning_column_type sysname
2007-03-21 14:42:58.07 declare @.qualified_source_object_name nvarchar(600)
2007-03-21 14:42:58.07 declare @.partitioning_column_collation sysname
2007-03-21 14:42:58.07 declare @.partitioning_index_name sysname
2007-03-21 14:42:58.07
2007-03-21 14:42:58.07 set @.qualified_source_object_name =
quotename(@.source_object_schema) + N'.' + quotename(@.source_object_name)
2007-03-21 14:42:58.07 set @.partitioning_column = null
2007-03-21 14:42:58.07 set @.partitioning_column_type = null
2007-03-21 14:42:58.07 set @.partitioning_index_name = null
2007-03-21 14:42:58.07
2007-03-21 14:42:58.07 select @.partitioning_column = sc.name,
2007-03-21 14:42:58.07 @.partitioning_column_type = st.name,
2007-03-21 14:42:58.07 @.partitioning_column_collation =
sc.collation,
2007-03-21 14:42:58.07 @.partitioning_index_name = si.name
2007-03-21 14:42:58.07 from sysindexes si
2007-03-21 14:42:58.07 inner join syscolumns sc
2007-03-21 14:42:58.07 on index_col(@.qualified_source_object_name,
si.indid, 1) = sc.name
2007-03-21 14:42:58.07 inner join systypes st
2007-03-21 14:42:58.07 on sc.xtype = st.xusertype
2007-03-21 14:42:58.07 where si.id = @.source_object_id
2007-03-21 14:42:58.07 and sc.id = @.sync_object_id
2007-03-21 14:42:58.07 and si.indid = 1
2007-03-21 14:42:58.07 and st.name in (N'uniqueidentifier', N'bit',
N'tinyint', N'smallint', N'int', N'smalldatetime', N'real', N'money',
N'datetime', N'float', N'bit', N'decimal', N'numeric', N'smallmoney',
N'bigint', N'varbinary', N'varchar', N'binary', N'char', N'timestamp',
N'nvarchar', N'nchar')
2007-03-21 14:42:58.07 and (@.use_primary_key_only = 0 or si.status &
2048 = 2048)
2007-03-21 14:42:58.07
2007-03-21 14:42:58.07 if @.partitioning_column is not null
2007-03-21 14:42:58.07 begin
2007-03-21 14:42:58.07 select @.partitioning_index_name,
@.partitioning_column, @.partitioning_column_type,
@.partitioning_column_collation
2007-03-21 14:42:58.07 dbcc
show_statistics(@.qualified_source_object_name, @.partitioning_index_name)
2007-03-21 14:42:58.07 end
2007-03-21 14:42:58.07 Parameters:
2007-03-21 14:42:58.07 @.source_object_name = STATE
2007-03-21 14:42:58.07 @.source_object_schema = dbo
2007-03-21 14:42:58.07 @.sync_object_name = syncobj_0x3737313837413543
2007-03-21 14:42:58.07 @.sync_object_schema = dbo
2007-03-21 14:42:58.07 @.use_primary_key_only = 0
2007-03-21 14:42:58.09
2007-03-21 14:42:58.09 SQL Command dump
2007-03-21 14:42:58.09 ================
2007-03-21 14:42:58.09 Server: NOMOS-SRVR
2007-03-21 14:42:58.09 Database: TEST
2007-03-21 14:42:58.09 Command Text: SET TRANSACTION ISOLATION LEVEL READ
COMMITTED;BEGIN TRANSACTION
2007-03-21 14:42:58.09 Parameters:
2007-03-21 14:42:58.09
2007-03-21 14:42:58.09 SQL Command dump
2007-03-21 14:42:58.09 ================
2007-03-21 14:42:58.09 Server: NOMOS-SRVR
2007-03-21 14:42:58.09 Database: TEST
2007-03-21 14:42:58.09 Command Text: update dbo.syssubscriptions with
(ROWLOCK READPAST) set status = status where artid in (select artid from
dbo.sysarticles arts inner join dbo.syspublications pubs on arts.pubid =
pubs.pubid where pubs.name = @.publication)
2007-03-21 14:42:58.09 Parameters:
2007-03-21 14:42:58.09 @.publication = TestPublication
2007-03-21 14:42:58.09 [0%] Locking published tables while generating the
snapshot
2007-03-21 14:42:58.09
2007-03-21 14:42:58.09 SQL Command dump
2007-03-21 14:42:58.09 ================
2007-03-21 14:42:58.09 Server: NOMOS-SRVR
2007-03-21 14:42:58.09 Database: TEST
2007-03-21 14:42:58.09 Command Text: SELECT * FROM [dbo].[STATE] WITH
(TABLOCK HOLDLOCK) WHERE 1 = 2
2007-03-21 14:42:58.09 Parameters:
2007-03-21 14:42:58.15 [0%] Bulk copying snapshot data for article 'STATE'
2007-03-21 14:42:58.18 [0%] Bulk copied snapshot data for article 'STATE' (4
rows).
2007-03-21 14:42:58.73
2007-03-21 14:42:58.73 SQL Command dump
2007-03-21 14:42:58.73 ================
2007-03-21 14:42:58.73 Server: NOMOS-SRVR
2007-03-21 14:42:58.73 Database: TEST
2007-03-21 14:42:58.73 Command Text: select count_big(*) from sys.tables
2007-03-21 14:42:58.73 Parameters:
2007-03-21 14:42:58.75 [7%] Pre-loading meta-data of all tables in the
publisher database for scripting
2007-03-21 14:42:59.64 [7%] Sorting article objects in the proper creation
order
2007-03-21 14:42:59.70
2007-03-21 14:42:59.70 SQL Command dump
2007-03-21 14:42:59.70 ================
2007-03-21 14:42:59.70 Server: NOMOS-SRVR
2007-03-21 14:42:59.70 Database: TEST
2007-03-21 14:42:59.70 Command Text:
2007-03-21 14:42:59.70 select distinct
2007-03-21 14:42:59.70 'name' = so.name,
2007-03-21 14:42:59.70 'schema' = schema_name(so.schema_id),
2007-03-21 14:42:59.70 'type' = rtrim(so.type)
2007-03-21 14:42:59.70 from sys.objects so
2007-03-21 14:42:59.70 inner join sys.sql_dependencies sd
2007-03-21 14:42:59.70 on so.object_id = sd.referenced_major_id
2007-03-21 14:42:59.70 where sd.object_id = object_id(@.qualified_name)
2007-03-21 14:42:59.70 and sd.object_id <> sd.referenced_major_id
2007-03-21 14:42:59.70 and upper(rtrim(so.type)) in ('U', 'P', 'PC', 'V',
'FN', 'TF', 'IF', 'FS', 'FT', 'AF', 'SN')
2007-03-21 14:42:59.70
2007-03-21 14:42:59.70 Parameters:
2007-03-21 14:42:59.70 @.qualified_name = [dbo].[STATE]
2007-03-21 14:42:59.71 [7%] Customizing object for scripting based on
article 'STATE'
2007-03-21 14:42:59.71 [7%] Resolving duplicate object names among
replicated objects
2007-03-21 14:42:59.84 [7%] Analyzing foreign key references among article
objects in the publication
2007-03-21 14:42:59.84 [7%] Analyzing external references of all replicated
check and default constraints
2007-03-21 14:42:59.84 [7%] Analyzing dependencies on non-article objects
2007-03-21 14:42:59.84 [7%] Generating schema scripts for article 'STATE'
2007-03-21 14:42:59.95
2007-03-21 14:42:59.95 SQL Command dump
2007-03-21 14:42:59.95 ================
2007-03-21 14:42:59.95 Server: NOMOS-SRVR
2007-03-21 14:42:59.95 Database: TEST
2007-03-21 14:42:59.95 Command Text: sp_scriptsubconflicttable
2007-03-21 14:42:59.95 Parameters:
2007-03-21 14:42:59.95 @.publication = TestPublication
2007-03-21 14:42:59.95 @.article = STATE
2007-03-21 14:42:59.95 [61%] Processing system pre-snapshot script
2007-03-21 14:42:59.96
2007-03-21 14:42:59.96 SQL Command dump
2007-03-21 14:42:59.96 ================
2007-03-21 14:42:59.96 Server: NOMOS-SRVR
2007-03-21 14:42:59.96 Database: TEST
2007-03-21 14:42:59.96 Command Text: declare @.lsn binary(10) exec
sp_replincrementlsn @.lsn OUTPUT select @.lsn
2007-03-21 14:42:59.96 Parameters:
2007-03-21 14:42:59.96
2007-03-21 14:42:59.96 SQL Command dump
2007-03-21 14:42:59.96 ================
2007-03-21 14:42:59.96 Server: NOMOS-SRVR
2007-03-21 14:42:59.96 Database: TEST
2007-03-21 14:42:59.96 Command Text: sp_MSactivate_auto_sub
2007-03-21 14:42:59.96 Parameters:
2007-03-21 14:42:59.96 @.publication = TestPublication
2007-03-21 14:42:59.96 @.article = %
2007-03-21 14:42:59.96 @.status = active
2007-03-21 14:42:59.96 @.skipobjectactivation = 1
2007-03-21 14:42:59.98
2007-03-21 14:42:59.98 SQL Command dump
2007-03-21 14:42:59.98 ================
2007-03-21 14:42:59.98 Server: NOMOS-SRVR
2007-03-21 14:42:59.98 Database: distribution
2007-03-21 14:42:59.98 Command Text: SET TRANSACTION ISOLATION LEVEL READ
COMMITTED;BEGIN TRANSACTION
2007-03-21 14:42:59.98 Parameters:
2007-03-21 14:42:59.98
2007-03-21 14:42:59.98 SQL Command dump
2007-03-21 14:42:59.98 ================
2007-03-21 14:42:59.98 Server: NOMOS-SRVR
2007-03-21 14:42:59.98 Database: distribution
2007-03-21 14:42:59.98 Command Text: sp_MSget_new_xact_seqno
2007-03-21 14:42:59.98 Parameters:
2007-03-21 14:42:59.98 @.publisher_id = 0
2007-03-21 14:42:59.98 @.publisher_db = TEST
2007-03-21 14:42:59.98 @.len = 14
2007-03-21 14:42:59.98 [61%] Posting snapshot commands into the distribution
database
2007-03-21 14:42:59.98
2007-03-21 14:42:59.98 SQL Command dump
2007-03-21 14:42:59.98 ================
2007-03-21 14:42:59.98 Server: NOMOS-SRVR
2007-03-21 14:42:59.98 Database: distribution
2007-03-21 14:42:59.98 Command Text: sp_MSadd_repl_command
2007-03-21 14:42:59.98 Parameters:
2007-03-21 14:42:59.98 @.publisher_id = 0
2007-03-21 14:42:59.98 @.publisher_db = TEST
2007-03-21 14:42:59.98 @.type = -2147483598
2007-03-21 14:42:59.98 @.article_id = 1
2007-03-21 14:42:59.98 @.xact_id = System.Byte[]
2007-03-21 14:42:59.98 @.xact_seqno = SqlBinary(14)
2007-03-21 14:42:59.98 @.command_id = 1
2007-03-21 14:42:59.98 @.partial_command = False
2007-03-21 14:42:59.98 @.command = System.Byte[]
2007-03-21 14:42:59.98
2007-03-21 14:42:59.98 SQL Command dump
2007-03-21 14:42:59.98 ================
2007-03-21 14:42:59.98 Server: NOMOS-SRVR
2007-03-21 14:42:59.98 Database: distribution
2007-03-21 14:42:59.98 Command Text: sp_MSadd_repl_command
2007-03-21 14:42:59.98 Parameters:
2007-03-21 14:42:59.98 @.publisher_id = 0
2007-03-21 14:42:59.98 @.publisher_db = TEST
2007-03-21 14:42:59.98 @.type = -2147483597
2007-03-21 14:42:59.98 @.article_id = 1
2007-03-21 14:42:59.98 @.xact_id = System.Byte[]
2007-03-21 14:42:59.98 @.xact_seqno = SqlBinary(14)
2007-03-21 14:42:59.98 @.command_id = 2
2007-03-21 14:42:59.98 @.partial_command = False
2007-03-21 14:42:59.98 @.command = System.Byte[]
2007-03-21 14:42:59.98
2007-03-21 14:42:59.98 SQL Command dump
2007-03-21 14:42:59.98 ================
2007-03-21 14:42:59.98 Server: NOMOS-SRVR
2007-03-21 14:42:59.98 Database: distribution
2007-03-21 14:42:59.98 Command Text: sp_MSadd_repl_command
2007-03-21 14:42:59.98 Parameters:
2007-03-21 14:42:59.98 @.publisher_id = 0
2007-03-21 14:42:59.98 @.publisher_db = TEST
2007-03-21 14:42:59.98 @.type = -2147483641
2007-03-21 14:42:59.98 @.article_id = 0
2007-03-21 14:42:59.98 @.xact_id = System.Byte[]
2007-03-21 14:42:59.98 @.xact_seqno = SqlBinary(14)
2007-03-21 14:42:59.98 @.command_id = 3
2007-03-21 14:42:59.98 @.partial_command = False
2007-03-21 14:42:59.98 @.command = System.Byte[]
2007-03-21 14:42:59.98
2007-03-21 14:42:59.98 SQL Command dump
2007-03-21 14:42:59.98 ================
2007-03-21 14:42:59.98 Server: NOMOS-SRVR
2007-03-21 14:42:59.98 Database: distribution
2007-03-21 14:42:59.98 Command Text: sp_MSadd_repl_command
2007-03-21 14:42:59.98 Parameters:
2007-03-21 14:42:59.98 @.publisher_id = 0
2007-03-21 14:42:59.98 @.publisher_db = TEST
2007-03-21 14:42:59.98 @.type = -2147483588
2007-03-21 14:42:59.98 @.article_id = 1
2007-03-21 14:42:59.98 @.xact_id = System.Byte[]
2007-03-21 14:42:59.98 @.xact_seqno = SqlBinary(14)
2007-03-21 14:42:59.98 @.command_id = 4
2007-03-21 14:42:59.98 @.partial_command = False
2007-03-21 14:42:59.98 @.command = System.Byte[]
2007-03-21 14:43:00.00
2007-03-21 14:43:00.00 SQL Command dump
2007-03-21 14:43:00.00 ================
2007-03-21 14:43:00.00 Server: NOMOS-SRVR
2007-03-21 14:43:00.00 Database: distribution
2007-03-21 14:43:00.00 Command Text: sp_MSadd_repl_command
2007-03-21 14:43:00.00 Parameters:
2007-03-21 14:43:00.00 @.publisher_id = 0
2007-03-21 14:43:00.00 @.publisher_db = TEST
2007-03-21 14:43:00.00 @.type = -2147483646
2007-03-21 14:43:00.00 @.article_id = 1
2007-03-21 14:43:00.00 @.xact_id = System.Byte[]
2007-03-21 14:43:00.00 @.xact_seqno = SqlBinary(14)
2007-03-21 14:43:00.00 @.command_id = 5
2007-03-21 14:43:00.00 @.partial_command = False
2007-03-21 14:43:00.00 @.command = System.Byte[]
2007-03-21 14:43:00.00 [61%] Inserted schema command for article 'STATE'
into the distribution database
2007-03-21 14:43:00.00
2007-03-21 14:43:00.00 SQL Command dump
2007-03-21 14:43:00.00 ================
2007-03-21 14:43:00.00 Server: NOMOS-SRVR
2007-03-21 14:43:00.00 Database: distribution
2007-03-21 14:43:00.00 Command Text: sp_MSadd_repl_command
Amything inside ?
"Hilary Cotter" wrote:

> Yes, please post the whole thing here. It sounds like you might have done
> this for the snapshot agent. You may need to do this for the
> merge/distribution agent as well.
> --
> Hilary Cotter
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
> Looking for a FAQ on Indexing Services/SQL FTS
> http://www.indexserverfaq.com
>
> "calderara" <calderara@.discussions.microsoft.com> wrote in message
> news:3243F73C-43DF-458A-837D-615F57DF16D4@.microsoft.com...
>
>
|||Here is is the next part of the file :
================================
2007-03-21 14:43:00.00 Parameters:
2007-03-21 14:43:00.00 @.publisher_id = 0
2007-03-21 14:43:00.00 @.publisher_db = TEST
2007-03-21 14:43:00.00 @.type = -2147483546
2007-03-21 14:43:00.00 @.article_id = 1
2007-03-21 14:43:00.00 @.xact_id = System.Byte[]
2007-03-21 14:43:00.00 @.xact_seqno = SqlBinary(14)
2007-03-21 14:43:00.00 @.command_id = 6
2007-03-21 14:43:00.00 @.partial_command = False
2007-03-21 14:43:00.00 @.command = System.Byte[]
2007-03-21 14:43:00.00
2007-03-21 14:43:00.00 SQL Command dump
2007-03-21 14:43:00.00 ================
2007-03-21 14:43:00.00 Server: NOMOS-SRVR
2007-03-21 14:43:00.00 Database: distribution
2007-03-21 14:43:00.00 Command Text: sp_MSadd_repl_command
2007-03-21 14:43:00.00 Parameters:
2007-03-21 14:43:00.00 @.publisher_id = 0
2007-03-21 14:43:00.00 @.publisher_db = TEST
2007-03-21 14:43:00.00 @.type = -2147483646
2007-03-21 14:43:00.00 @.article_id = 1
2007-03-21 14:43:00.00 @.xact_id = System.Byte[]
2007-03-21 14:43:00.00 @.xact_seqno = SqlBinary(14)
2007-03-21 14:43:00.00 @.command_id = 7
2007-03-21 14:43:00.00 @.partial_command = False
2007-03-21 14:43:00.00 @.command = System.Byte[]
2007-03-21 14:43:00.00 [61%] Inserted index creation command for article
'STATE' into the distribution database.
2007-03-21 14:43:00.00
2007-03-21 14:43:00.00 SQL Command dump
2007-03-21 14:43:00.00 ================
2007-03-21 14:43:00.00 Server: NOMOS-SRVR
2007-03-21 14:43:00.00 Database: distribution
2007-03-21 14:43:00.00 Command Text: sp_MSadd_repl_command
2007-03-21 14:43:00.00 Parameters:
2007-03-21 14:43:00.00 @.publisher_id = 0
2007-03-21 14:43:00.00 @.publisher_db = TEST
2007-03-21 14:43:00.00 @.type = -2147483645
2007-03-21 14:43:00.00 @.article_id = 1
2007-03-21 14:43:00.00 @.xact_id = System.Byte[]
2007-03-21 14:43:00.00 @.xact_seqno = SqlBinary(14)
2007-03-21 14:43:00.00 @.command_id = 8
2007-03-21 14:43:00.00 @.partial_command = False
2007-03-21 14:43:00.00 @.command = System.Byte[]
2007-03-21 14:43:00.00 [61%] Inserted bcp command for article 'STATE' into
the distribution database.
2007-03-21 14:43:00.00
2007-03-21 14:43:00.00 SQL Command dump
2007-03-21 14:43:00.00 ================
2007-03-21 14:43:00.00 Server: NOMOS-SRVR
2007-03-21 14:43:00.00 Database: TEST
2007-03-21 14:43:00.00 Command Text: sp_MSget_synctran_commands
2007-03-21 14:43:00.00 Parameters:
2007-03-21 14:43:00.00 @.publication = TestPublication
2007-03-21 14:43:00.01
2007-03-21 14:43:00.01 SQL Command dump
2007-03-21 14:43:00.01 ================
2007-03-21 14:43:00.01 Server: NOMOS-SRVR
2007-03-21 14:43:00.01 Database: distribution
2007-03-21 14:43:00.01 Command Text: sp_MSadd_repl_command
2007-03-21 14:43:00.01 Parameters:
2007-03-21 14:43:00.01 @.publisher_id = 0
2007-03-21 14:43:00.01 @.publisher_db = TEST
2007-03-21 14:43:00.01 @.type = -2147483596
2007-03-21 14:43:00.01 @.article_id = 1
2007-03-21 14:43:00.01 @.xact_id = System.Byte[]
2007-03-21 14:43:00.01 @.xact_seqno = SqlBinary(14)
2007-03-21 14:43:00.01 @.command_id = 9
2007-03-21 14:43:00.01 @.partial_command = False
2007-03-21 14:43:00.01 @.command = System.Byte[]
2007-03-21 14:43:00.01
2007-03-21 14:43:00.01 SQL Command dump
2007-03-21 14:43:00.01 ================
2007-03-21 14:43:00.01 Server: NOMOS-SRVR
2007-03-21 14:43:00.01 Database: distribution
2007-03-21 14:43:00.01 Command Text: sp_MSlock_auto_sub
2007-03-21 14:43:00.01 Parameters:
2007-03-21 14:43:00.01 @.publisher_id = 0
2007-03-21 14:43:00.01 @.publisher_db = TEST
2007-03-21 14:43:00.01 @.publication = TestPublication
2007-03-21 14:43:00.01 @.reset = 1
2007-03-21 14:43:00.01
2007-03-21 14:43:00.01 SQL Command dump
2007-03-21 14:43:00.01 ================
2007-03-21 14:43:00.01 Server: NOMOS-SRVR
2007-03-21 14:43:00.01 Database: distribution
2007-03-21 14:43:00.01 Command Text: sp_MSset_snapshot_xact_seqno
2007-03-21 14:43:00.01 Parameters:
2007-03-21 14:43:00.01 @.publisher_id = 0
2007-03-21 14:43:00.01 @.publisher_db = TEST
2007-03-21 14:43:00.01 @.article_id = 1
2007-03-21 14:43:00.01 @.xact_seqno = SqlBinary(14)
2007-03-21 14:43:00.01 @.reset = 1
2007-03-21 14:43:00.01 @.publisher_seqno = SqlBinary(10)
2007-03-21 14:43:00.01 @.ss_cplt_seqno = Null
2007-03-21 14:43:00.01
2007-03-21 14:43:00.01 SQL Command dump
2007-03-21 14:43:00.01 ================
2007-03-21 14:43:00.01 Server: NOMOS-SRVR
2007-03-21 14:43:00.01 Database: distribution
2007-03-21 14:43:00.01 Command Text: sp_MSdist_activate_auto_sub
2007-03-21 14:43:00.01 Parameters:
2007-03-21 14:43:00.01 @.publisher_id = 0
2007-03-21 14:43:00.01 @.publisher_db = TEST
2007-03-21 14:43:00.01 @.article_id = 1
2007-03-21 14:43:00.01
2007-03-21 14:43:00.01 SQL Command dump
2007-03-21 14:43:00.01 ================
2007-03-21 14:43:00.01 Server: NOMOS-SRVR
2007-03-21 14:43:00.01 Database: distribution
2007-03-21 14:43:00.01 Command Text: COMMIT TRANSACTION
2007-03-21 14:43:00.01 Parameters:
2007-03-21 14:43:00.01
2007-03-21 14:43:00.01 SQL Command dump
2007-03-21 14:43:00.01 ================
2007-03-21 14:43:00.01 Server: NOMOS-SRVR
2007-03-21 14:43:00.01 Database: TEST
2007-03-21 14:43:00.01 Command Text: COMMIT TRANSACTION
2007-03-21 14:43:00.01 Parameters:
2007-03-21 14:43:00.03 [100%] A snapshot of 1 article(s) was generated.
2007-03-21 14:43:00.03 *************************** Performance Statistics
****************************
2007-03-21 14:43:00.03 Overall snapshot generation time (seconds): 2,05
2007-03-21 14:43:00.03 Total number of rows bulk-copied from published
objects: 4
2007-03-21 14:43:00.03 Time spent generating schema scripts (seconds): 1,59
2007-03-21 14:43:00.03 Time spent pre-loading database objects for scripting
(seconds): 1,44
2007-03-21 14:43:00.03 Time spent analyzing article object dependencies
(seconds): 0,05
2007-03-21 14:43:00.03 Time spent customizing article objects for scripting
(seconds): 0,00
2007-03-21 14:43:00.03 Time spent resolving duplicate object names
(seconds): 0,00
2007-03-21 14:43:00.03 Time spent analyzing foreign key references
(seconds): 0,00
2007-03-21 14:43:00.03 Time spent analyzing check and default constraint
references (seconds): 0,00
2007-03-21 14:43:00.03 Time spent analyzing non-article object dependencies
(seconds): 0,00
2007-03-21 14:43:00.03 Time spent preparing snapshot generation (seconds):
0,11
2007-03-21 14:43:00.03 Time spent bulk copying data (seconds): 0,09
2007-03-21 14:43:00.03 Time spent copying/compressing generated file
(seconds): 0,00
2007-03-21 14:43:00.03 Time spent posting snapshot commands (seconds): 0,06
2007-03-21 14:43:00.03
************************************************** *****************************
2007-03-21 14:43:00.04
2007-03-21 14:43:00.04 SQL Command dump
2007-03-21 14:43:00.04 ================
2007-03-21 14:43:00.04 Server: NOMOS-SRVR
2007-03-21 14:43:00.04 Database: TEST
2007-03-21 14:43:00.04 Command Text: sys.sp_releaseapplock
2007-03-21 14:43:00.04 Parameters:
2007-03-21 14:43:00.04 @.Resource = NOMOS-SRVR-TEST-TestPublication-1
2007-03-21 14:43:00.04 @.LockOwner = Session
2007-03-21 14:43:00.04 @.DbPrincipal = db_owner
================================================== ===
"Hilary Cotter" wrote:

> Yes, please post the whole thing here. It sounds like you might have done
> this for the snapshot agent. You may need to do this for the
> merge/distribution agent as well.
> --
> Hilary Cotter
> Looking for a SQL Server replication book?
> http://www.nwsu.com/0974973602.html
> Looking for a FAQ on Indexing Services/SQL FTS
> http://www.indexserverfaq.com
>
> "calderara" <calderara@.discussions.microsoft.com> wrote in message
> news:3243F73C-43DF-458A-837D-615F57DF16D4@.microsoft.com...
>
>

Replication between servers

Hi all
My company is using Microsoft SQL Server 2000 on a Windows 2000 server, in
its head office location. We have a second office, which is connected to
head office via a 2Mb fixed link - users of the databases in that second
office are connecting directly to the server in the head office. However,
we've realised that if our head office system fails, either through natural
disaster or sabotage, our second office will have no database functionality.
With that in mind, we are considering purchasing a second database server,
and putting it into the satellite office. However, users in both offices
would have to be able to use the same database, which handles about 20,000
record entries per day. My manager has asked me to find out how we would
set it up so that users in the head office can be connected to the head
office server, and users in the second office are connected to the second
server, and the data is then being effectively and efficiently merged.
To give a further understanding of the particular database that I'm thinking
of, the users are creating records in a total of four tables. Each of the
four tables has an identity field which is the primary key. However, three
of the four tables have a foreign key which links back to the fourth table.
Therefore, there can be no possibility of users at both sites generating the
same ID numbers.
TIA
Ian Henderson
"Ian Henderson" <ianhendersonis@.hotmail.com> wrote in message
news:d078kv$o50$1$8302bc10@.news.demon.co.uk...

> My company is using Microsoft SQL Server 2000 on a Windows 2000 server, in
> its head office location. We have a second office, which is connected to
> head office via a 2Mb fixed link - users of the databases in that second
> office are connecting directly to the server in the head office. However,
> we've realised that if our head office system fails, either through
natural
> disaster or sabotage, our second office will have no database
functionality.
> With that in mind, we are considering purchasing a second database server,
> and putting it into the satellite office. However, users in both offices
> would have to be able to use the same database, which handles about 20,000
> record entries per day. My manager has asked me to find out how we would
> set it up so that users in the head office can be connected to the head
> office server, and users in the second office are connected to the second
> server, and the data is then being effectively and efficiently merged.
> To give a further understanding of the particular database that I'm
thinking
> of, the users are creating records in a total of four tables. Each of the
> four tables has an identity field which is the primary key. However,
three
> of the four tables have a foreign key which links back to the fourth
table.
> Therefore, there can be no possibility of users at both sites generating
the
> same ID numbers.
Several solutions come to mind, from simple to more complex.
1) Providing your users are satisfied with the performance over the WAN
link --
Once you've got a second SQL Server running at the office, set up log
shipping so you have a fairly close copy of the primary SQL Server. In the
event of a failure of the primary location SQL Server or office, you could
point your users to the (now) local copy and continue working.
2) You could consider setting up merge replication, where updates take place
at each local office and the updates are replicated (merged) between SQL
Servers. Your last paragraph tells me you've thought about the implications
of the primary key creation. You do want to avoid replication conflicts, and
the design phase is the place to do that. See the following link on
replication to consider the other replication alternatives:
http://www.microsoft.com/sql/evaluat...eplication.asp
Steve

Replication between servers

Hi all
My company is using Microsoft SQL Server 2000 on a Windows 2000 server, in
its head office location. We have a second office, which is connected to
head office via a 2Mb fixed link - users of the databases in that second
office are connecting directly to the server in the head office. However,
we've realised that if our head office system fails, either through natural
disaster or sabotage, our second office will have no database functionality.
With that in mind, we are considering purchasing a second database server,
and putting it into the satellite office. However, users in both offices
would have to be able to use the same database, which handles about 20,000
record entries per day. My manager has asked me to find out how we would
set it up so that users in the head office can be connected to the head
office server, and users in the second office are connected to the second
server, and the data is then being effectively and efficiently merged.
To give a further understanding of the particular database that I'm thinking
of, the users are creating records in a total of four tables. Each of the
four tables has an identity field which is the primary key. However, three
of the four tables have a foreign key which links back to the fourth table.
Therefore, there can be no possibility of users at both sites generating the
same ID numbers.
TIA
Ian Henderson"Ian Henderson" <ianhendersonis@.hotmail.com> wrote in message
news:d078kv$o50$1$8302bc10@.news.demon.co.uk...
> My company is using Microsoft SQL Server 2000 on a Windows 2000 server, in
> its head office location. We have a second office, which is connected to
> head office via a 2Mb fixed link - users of the databases in that second
> office are connecting directly to the server in the head office. However,
> we've realised that if our head office system fails, either through
natural
> disaster or sabotage, our second office will have no database
functionality.
> With that in mind, we are considering purchasing a second database server,
> and putting it into the satellite office. However, users in both offices
> would have to be able to use the same database, which handles about 20,000
> record entries per day. My manager has asked me to find out how we would
> set it up so that users in the head office can be connected to the head
> office server, and users in the second office are connected to the second
> server, and the data is then being effectively and efficiently merged.
> To give a further understanding of the particular database that I'm
thinking
> of, the users are creating records in a total of four tables. Each of the
> four tables has an identity field which is the primary key. However,
three
> of the four tables have a foreign key which links back to the fourth
table.
> Therefore, there can be no possibility of users at both sites generating
the
> same ID numbers.
Several solutions come to mind, from simple to more complex.
1) Providing your users are satisfied with the performance over the WAN
link --
Once you've got a second SQL Server running at the office, set up log
shipping so you have a fairly close copy of the primary SQL Server. In the
event of a failure of the primary location SQL Server or office, you could
point your users to the (now) local copy and continue working.
2) You could consider setting up merge replication, where updates take place
at each local office and the updates are replicated (merged) between SQL
Servers. Your last paragraph tells me you've thought about the implications
of the primary key creation. You do want to avoid replication conflicts, and
the design phase is the place to do that. See the following link on
replication to consider the other replication alternatives:
http://www.microsoft.com/sql/evaluation/features/replication.asp
Steve

Replication between servers

Hi all
My company is using Microsoft SQL Server 2000 on a Windows 2000 server, in
its head office location. We have a second office, which is connected to
head office via a 2Mb fixed link - users of the databases in that second
office are connecting directly to the server in the head office. However,
we've realised that if our head office system fails, either through natural
disaster or sabotage, our second office will have no database functionality.
With that in mind, we are considering purchasing a second database server,
and putting it into the satellite office. However, users in both offices
would have to be able to use the same database, which handles about 20,000
record entries per day. My manager has asked me to find out how we would
set it up so that users in the head office can be connected to the head
office server, and users in the second office are connected to the second
server, and the data is then being effectively and efficiently merged.
To give a further understanding of the particular database that I'm thinking
of, the users are creating records in a total of four tables. Each of the
four tables has an identity field which is the primary key. However, three
of the four tables have a foreign key which links back to the fourth table.
Therefore, there can be no possibility of users at both sites generating the
same ID numbers.
TIA
Ian Henderson
"Ian Henderson" <ianhendersonis@.hotmail.com> wrote in message
news:d078kv$o50$1$8302bc10@.news.demon.co.uk...

> My company is using Microsoft SQL Server 2000 on a Windows 2000 server, in
> its head office location. We have a second office, which is connected to
> head office via a 2Mb fixed link - users of the databases in that second
> office are connecting directly to the server in the head office. However,
> we've realised that if our head office system fails, either through
natural
> disaster or sabotage, our second office will have no database
functionality.
> With that in mind, we are considering purchasing a second database server,
> and putting it into the satellite office. However, users in both offices
> would have to be able to use the same database, which handles about 20,000
> record entries per day. My manager has asked me to find out how we would
> set it up so that users in the head office can be connected to the head
> office server, and users in the second office are connected to the second
> server, and the data is then being effectively and efficiently merged.
> To give a further understanding of the particular database that I'm
thinking
> of, the users are creating records in a total of four tables. Each of the
> four tables has an identity field which is the primary key. However,
three
> of the four tables have a foreign key which links back to the fourth
table.
> Therefore, there can be no possibility of users at both sites generating
the
> same ID numbers.
Several solutions come to mind, from simple to more complex.
1) Providing your users are satisfied with the performance over the WAN
link --
Once you've got a second SQL Server running at the office, set up log
shipping so you have a fairly close copy of the primary SQL Server. In the
event of a failure of the primary location SQL Server or office, you could
point your users to the (now) local copy and continue working.
2) You could consider setting up merge replication, where updates take place
at each local office and the updates are replicated (merged) between SQL
Servers. Your last paragraph tells me you've thought about the implications
of the primary key creation. You do want to avoid replication conflicts, and
the design phase is the place to do that. See the following link on
replication to consider the other replication alternatives:
http://www.microsoft.com/sql/evaluat...eplication.asp
Steve

Replication between servers

Hi all
My company is using Microsoft SQL Server 2000 on a Windows 2000 server, in
its head office location. We have a second office, which is connected to
head office via a 2Mb fixed link - users of the databases in that second
office are connecting directly to the server in the head office. However,
we've realised that if our head office system fails, either through natural
disaster or sabotage, our second office will have no database functionality.
With that in mind, we are considering purchasing a second database server,
and putting it into the satellite office. However, users in both offices
would have to be able to use the same database, which handles about 20,000
record entries per day. My manager has asked me to find out how we would
set it up so that users in the head office can be connected to the head
office server, and users in the second office are connected to the second
server, and the data is then being effectively and efficiently merged.
To give a further understanding of the particular database that I'm thinking
of, the users are creating records in a total of four tables. Each of the
four tables has an identity field which is the primary key. However, three
of the four tables have a foreign key which links back to the fourth table.
Therefore, there can be no possibility of users at both sites generating the
same ID numbers.
TIA
Ian Henderson
"Ian Henderson" <ianhendersonis@.hotmail.com> wrote in message
news:d078kv$o50$1$8302bc10@.news.demon.co.uk...

> My company is using Microsoft SQL Server 2000 on a Windows 2000 server, in
> its head office location. We have a second office, which is connected to
> head office via a 2Mb fixed link - users of the databases in that second
> office are connecting directly to the server in the head office. However,
> we've realised that if our head office system fails, either through
natural
> disaster or sabotage, our second office will have no database
functionality.
> With that in mind, we are considering purchasing a second database server,
> and putting it into the satellite office. However, users in both offices
> would have to be able to use the same database, which handles about 20,000
> record entries per day. My manager has asked me to find out how we would
> set it up so that users in the head office can be connected to the head
> office server, and users in the second office are connected to the second
> server, and the data is then being effectively and efficiently merged.
> To give a further understanding of the particular database that I'm
thinking
> of, the users are creating records in a total of four tables. Each of the
> four tables has an identity field which is the primary key. However,
three
> of the four tables have a foreign key which links back to the fourth
table.
> Therefore, there can be no possibility of users at both sites generating
the
> same ID numbers.
Several solutions come to mind, from simple to more complex.
1) Providing your users are satisfied with the performance over the WAN
link --
Once you've got a second SQL Server running at the office, set up log
shipping so you have a fairly close copy of the primary SQL Server. In the
event of a failure of the primary location SQL Server or office, you could
point your users to the (now) local copy and continue working.
2) You could consider setting up merge replication, where updates take place
at each local office and the updates are replicated (merged) between SQL
Servers. Your last paragraph tells me you've thought about the implications
of the primary key creation. You do want to avoid replication conflicts, and
the design phase is the place to do that. See the following link on
replication to consider the other replication alternatives:
http://www.microsoft.com/sql/evaluat...eplication.asp
Steve
sql

Replication between servers

Hi all
My company is using Microsoft SQL Server 2000 on a Windows 2000 server, in
its head office location. We have a second office, which is connected to
head office via a 2Mb fixed link - users of the databases in that second
office are connecting directly to the server in the head office. However,
we've realised that if our head office system fails, either through natural
disaster or sabotage, our second office will have no database functionality.
With that in mind, we are considering purchasing a second database server,
and putting it into the satellite office. However, users in both offices
would have to be able to use the same database, which handles about 20,000
record entries per day. My manager has asked me to find out how we would
set it up so that users in the head office can be connected to the head
office server, and users in the second office are connected to the second
server, and the data is then being effectively and efficiently merged.
To give a further understanding of the particular database that I'm thinking
of, the users are creating records in a total of four tables. Each of the
four tables has an identity field which is the primary key. However, three
of the four tables have a foreign key which links back to the fourth table.
Therefore, there can be no possibility of users at both sites generating the
same ID numbers.
TIA
Ian Henderson"Ian Henderson" <ianhendersonis@.hotmail.com> wrote in message
news:d078kv$o50$1$8302bc10@.news.demon.co.uk...

> My company is using Microsoft SQL Server 2000 on a Windows 2000 server, in
> its head office location. We have a second office, which is connected to
> head office via a 2Mb fixed link - users of the databases in that second
> office are connecting directly to the server in the head office. However,
> we've realised that if our head office system fails, either through
natural
> disaster or sabotage, our second office will have no database
functionality.
> With that in mind, we are considering purchasing a second database server,
> and putting it into the satellite office. However, users in both offices
> would have to be able to use the same database, which handles about 20,000
> record entries per day. My manager has asked me to find out how we would
> set it up so that users in the head office can be connected to the head
> office server, and users in the second office are connected to the second
> server, and the data is then being effectively and efficiently merged.
> To give a further understanding of the particular database that I'm
thinking
> of, the users are creating records in a total of four tables. Each of the
> four tables has an identity field which is the primary key. However,
three
> of the four tables have a foreign key which links back to the fourth
table.
> Therefore, there can be no possibility of users at both sites generating
the
> same ID numbers.
Several solutions come to mind, from simple to more complex.
1) Providing your users are satisfied with the performance over the WAN
link --
Once you've got a second SQL Server running at the office, set up log
shipping so you have a fairly close copy of the primary SQL Server. In the
event of a failure of the primary location SQL Server or office, you could
point your users to the (now) local copy and continue working.
2) You could consider setting up merge replication, where updates take place
at each local office and the updates are replicated (merged) between SQL
Servers. Your last paragraph tells me you've thought about the implications
of the primary key creation. You do want to avoid replication conflicts, and
the design phase is the place to do that. See the following link on
replication to consider the other replication alternatives:
http://www.microsoft.com/sql/evalua...replication.asp
Steve

Replication between offices

Hi. I work for a building company and they have about 20 sales offices spread throughout the city. We have the main server in the corp office with SQL Server 2000 and then each sales office will have will have a computer with MSDE 2000 on it. We are trying to replicate from the sales office up to the main server and then replicate that data out to all of the sales offices. Also occasionally the sales offices will be disconnected because of someone running over the line or some other reason so the offices will be connected but not all of the time. Merge Replication using a pull subscription seems the best way to go about it. But if anyone has any suggestions on another way to do this or hints that would be greatly appreciated.May refer to this link (http://vyaskn.tripod.com/repl_ques.htm) for more information.sql

Replication between branches

Good Morning,
I have a dude with a new SQL implementation.
The scenario is a Central office with an SQL server and 10 branch offices
with sql server too. I need to replicate branches data Base with the central
sql.
All the branches could see the same DB.
It is possible to implement with SQL standard?
Or I need the Enterprise edition?
Thanks
Yes - Standard Edition is fine. You might also want to take a look here:
http://www.replicationanswers.com/CentralSubscriberArticle.asp
It might be that this is not the correct implementation - depends on other
factors eg can the branches change each other's data or is it completely
segregated?
Paul Ibison
|||Paul,
The Data can be changed by all the branches.
"Paul Ibison" wrote:

> Yes - Standard Edition is fine. You might also want to take a look here:
> http://www.replicationanswers.com/CentralSubscriberArticle.asp
> It might be that this is not the correct implementation - depends on other
> factors eg can the branches change each other's data or is it completely
> segregated?
> Paul Ibison
>