Replication Configuration Helper (Id buy it!)

Let's face it - setting up SQL 2005 merge pull replication using HTTPS between numerous SQL Server 2005 Express clients and one or more Publishers is an overly complicated exercise.

It should be easy. Why is it so hard?

In a nutshell: The connection chain and security chain is long and when there's a problem the error messages just don't point you to the answer - You have to search for it;re-read the doco; talk to gurus; use logging tools;re-read the error message 100 times; etc. etc.

It should be possible to create a 'Replication Configuration Helper' that steps -step by step - through both the connection chain (App - to SQL Express - to local network components - to the TCP/IP network - to the web server - to the publishers/distributers) and through the security chain (App - to SQL Express authentication - local agents including certificate errors - to ISS server authentication - to Distributer authentication -to Publisher authentication to Article authentication).

Let's face it - the steps occur in sequence and each step can be tested and the appropriate error message raised - TOGETHER WITH INSTRUCTIONS ON HOW TO RESOLVE! (I mean - what's use is an error message when you have to cut and past the error message into a browser and search for ages before you get the instructions on how to resolve the problem?)

So c'mon - someone volenteer to write a 'Replication Configuration Helper'

We are always looking to improve documentation, and we actually have an article in the works with regards to web sync with no release date yet, if you haven't noticed it's a very popular topic on this forum. We'll continue to update msdn, online version of books online, and kb articles on an ongoing basis and as needed. Thanks for your feedback.sql

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 SQL Express 2005

Hi All,

I am trying to do a Replication between a network SQL Server Express Edition 2005 DB with a client SQL Server Express Edition 2005 DB. My question is

1. Can we do replicaiton between SQL Server Express Edition 2005. (No SQL SERVER present)

2. If yes can any of you provide me some guidance or some pointers on how to achieve it.

Thanks

Suresh

Quick answer is no. Check out the following posting for more info.

http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=941980&SiteID=1

Gary

Replication between SQL 2005 Express Edition and SQL 2005 Standard Edition

Hello everybody,

I got a problem in my development phase. I'm developing a web-application system that running merge database technology which is centralized database and distributed database. This is because my customer want a highly optimum system standby.

My centralized database running SQL Server 2005 Standard Edition and the distributed database running SQL Server 2005 Express Edition (because it is free). Each of these database, the users can change the data on its database. So, every database must have the same data. from my understanding, each server must act as Publisher and Subscriber. Can SQL Server 2005 Express Edition be a Publisher?

If not, what the solution you all may suggest, because cost is the first factor. If my architecture is not correct, so what you all suggest to me to resolve the problem.

Thanks so much. Any suggestion and opinion is highly appreciate and I'm highly thanks to you all.

You cannot republish with SQL Express, you need Standard Edition or higher. As for solutions, see if you can try to not republish and use the single publisher scenario, or pay for Standard Edition. If cost is a factor, then you have to weigh $$$ versus not being able to meet your business requirements.|||If your intent is that you want the Standard and the express editions to be in sync, and that you want the DML that happen at the Express to be sent to the Standard edition too, you dont need to make the Express as a publisher. By default when you setup merge replication between 2 nodes, they both are read-write. That is Express site and do DML and the merge agent can send across these DML to the Standard edition site.

Replication between 2 or more SQL Express databases

Problem description
There is one central SQL Express database. And one (or more) SQL Express
database(s) on remote locations. This approach is mandatory due to some
application features later-on.
The local database(s) on the remote location(s) will act as a sort of backup
in case there is no network connection. Meaning that the data is stored
locally at all times. And moved to the central database once the network
connection is on.
Updates to the local database(s) should trigger a process where all data is
moved to the central database if there is a network connection. So for now,
it’s a one way stream: remote to central.
This approach gives us the option to delay the moves - if needed. For
example, the daily data is kept local and moved to the central site over
night. Which is a good thing to have if network resources are limited during
office hours.
Solution
To make this happen, I was thinking allong the lines of using triggered
stored procedures.
Where a local database update triggers a stored procedure that checks the
network connection and performs the move to the central database.
If there is more than one record in the remote database, all records are
moved to the central database. Also, an entry should be added to a log-file.
If the network connection is not there for whatever reason, an entry should
be written in a log-file stating that there was no connection to the central
database.
Options
Another way of solving this is using RMO-based publications and subscribers.
Where the database on the remote locations are publishers. And the central
database are subscribers. However, according to Microsoft:
- SQL Express can only act as a subscriber.
- Data is copied. And not moved.
According to the SQL-BOL, the first limitation doesn’t exist when using
programmatic, transactional replication.
However, the second needs to be solved as well. And in the examples of
SQL-BOL, this is not mentioned. At least not that I’m aware of.
There are some advantages using RMO. For example deploying a new version of
the application. Or deploying an updated database schema. Please let me know
if this is proven to be really usefull. If so, this would be the preferred
method – provided that the limitations mentioned earlier are solved. And if
using this method, I would prefer stored procedures or Visual Basic for
programming this.
Help wanted
Since I’m a newbie on these replication matters, I would like some help with
this.
Who is willing to help with examples and suggestions?
Sofar, I’ve been able to:
- Install SQL Express with network connections enabled
- Running the Management Studio and create the data model I would like to use
- Add data manually and via an ODBC connection (using a system wide DSN).
- Run SQL select commands against the added data.
So the infrastructure is up and running….
firing triggers over the network is not scalable, as there is significant
latency involved for each trigger firing. For a batch operation it is
painful. Your transactions will also hang for up to 20 seconds if the
connection is down.
You might want to look at SSIS (Integration Services) or perhaps even bcp
for what you are trying to do.
You might also want to upgrade from Express to Standard so you can do
transactional replication which will do exactly what you are trying to do.
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
"Will" <Will@.discussions.microsoft.com> wrote in message
news:474B4797-1811-4ADC-8576-0137A4FCBAF9@.microsoft.com...
> Problem description
> --
> There is one central SQL Express database. And one (or more) SQL Express
> database(s) on remote locations. This approach is mandatory due to some
> application features later-on.
> The local database(s) on the remote location(s) will act as a sort of
> backup
> in case there is no network connection. Meaning that the data is stored
> locally at all times. And moved to the central database once the network
> connection is on.
> Updates to the local database(s) should trigger a process where all data
> is
> moved to the central database if there is a network connection. So for
> now,
> it's a one way stream: remote to central.
> This approach gives us the option to delay the moves - if needed. For
> example, the daily data is kept local and moved to the central site over
> night. Which is a good thing to have if network resources are limited
> during
> office hours.
> Solution
> --
> To make this happen, I was thinking allong the lines of using triggered
> stored procedures.
> Where a local database update triggers a stored procedure that checks the
> network connection and performs the move to the central database.
> If there is more than one record in the remote database, all records are
> moved to the central database. Also, an entry should be added to a
> log-file.
> If the network connection is not there for whatever reason, an entry
> should
> be written in a log-file stating that there was no connection to the
> central
> database.
> Options
> Another way of solving this is using RMO-based publications and
> subscribers.
> Where the database on the remote locations are publishers. And the central
> database are subscribers. However, according to Microsoft:
> - SQL Express can only act as a subscriber.
> - Data is copied. And not moved.
> According to the SQL-BOL, the first limitation doesn't exist when using
> programmatic, transactional replication.
> However, the second needs to be solved as well. And in the examples of
> SQL-BOL, this is not mentioned. At least not that I'm aware of.
> There are some advantages using RMO. For example deploying a new version
> of
> the application. Or deploying an updated database schema. Please let me
> know
> if this is proven to be really usefull. If so, this would be the preferred
> method - provided that the limitations mentioned earlier are solved. And
> if
> using this method, I would prefer stored procedures or Visual Basic for
> programming this.
> Help wanted
> --
> Since I'm a newbie on these replication matters, I would like some help
> with
> this.
> Who is willing to help with examples and suggestions?
> Sofar, I've been able to:
> - Install SQL Express with network connections enabled
> - Running the Management Studio and create the data model I would like to
> use
> - Add data manually and via an ODBC connection (using a system wide DSN).
> - Run SQL select commands against the added data.
> So the infrastructure is up and running..
>
|||Hi Hilary,
Thanks for your support and feedback. I really do appreciate this!!!

> firing triggers over the network is not scalable, as there is significant
> latency involved for each trigger firing. For a batch operation it is
> painful. Your transactions will also hang for up to 20 seconds if the
> connection is down.
Mmm - sounds like we have a different understanding of the term trigger.
I would like to use triggers on the remote databases - not the central one.
As a result, triggers are not travelling across the network.

> You might want to look at SSIS (Integration Services) or perhaps even bcp
> for what you are trying to do.
I looked at SSIS. That would require
I'm not familiar with BCP. But it looks like a bulk COPY tool.
How would this help in MOVING the data?

> You might also want to upgrade from Express to Standard so you can do
> transactional replication which will do exactly what you are trying to do.
Do you mean replace Express with standaard on the remote side?
On the central side? Or both?
Keep in mind that SQL Express on the remote sites needs to run on
Workstations.
Ans therefor requires a light footprint.
Will
|||Answers inline.
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
"Will" <Will@.discussions.microsoft.com> wrote in message
news:E6201678-BFD9-4290-ABAC-1D7A5F6E1962@.microsoft.com...
> Hi Hilary,
> Thanks for your support and feedback. I really do appreciate this!!!
>
> Mmm - sounds like we have a different understanding of the term trigger.
> I would like to use triggers on the remote databases - not the central
> one.
> As a result, triggers are not travelling across the network.
>
> I looked at SSIS. That would require
> I'm not familiar with BCP. But it looks like a bulk COPY tool.
> How would this help in MOVING the data?
>
it doesn't move data, it copies it row by row. I know of no technology
which actually moves that, all copy it and you have to delete it yourself on
the source.

> Do you mean replace Express with standaard on the remote side?
> On the central side? Or both?
> Keep in mind that SQL Express on the remote sites needs to run on
> Workstations.
> Ans therefor requires a light footprint.
In retrospect you will probably need a code solution. Put a timestamp on
your tables which you can use to determine which rows have changed since the
last time you "moved" data. Anything greater than the timestamp the last
time you polled must be moved.
You will probably be able to use any version of SQL Server for this.
> --
> Will
>

Replicating to SQL 2000/2005 Express

We would like to replicate from SQL 2000/2005 Enterprise Edition to its
Express version and wanted to know if there we any issues around it. This
would be transactional replication
Hassan,
the main distinction that I know of is that for pull subscriptions there is
the limitation of Windows Synchronization Manager or RMO. Also obviously
there can be no republishing.
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com .

Replicating Sql Server to Express Edition as backup application

Hello!

We are running a business critical client-server application that needs to have high availability to the end user.
I was wondering if it would be possible to setup a replication/data transfer from an existing Sql Server 7.0/8.0/9.0 (regular online environment running on server) TO an instance of Sql 2005 Express Edition (backup env. running on klient PC).
In case of server failure the application would redirect - accessing the local PC Express edition.

Does anyone have any input on this, and if it would be a possible alternative to use as extra standby- system. ?

Kind regards
TomasYes this is possible but there are certain exceptions.
And it depends on what kind of replication technology you are looking at.
SQL Server 2005 Books Online has more information on supported topologies.

Search for "Using Multiple Versions of SQL Server in a Replication Topology"|||

Hi Tomas.

It would appear that I have a similar type of need. See this post http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=677662&SiteID=1 which describes my situation. If you've got any further info on how this is achieved please respond. I'll do the same. We were able to create the windows form app and use Sql2005 Std to maintain a 'gold' standard db on our publisher/distributor machine. We have to replace our db daily with an entirely new dataset that is sent to us via a foreign host. We take that data an bulk copy it into our db. Then, we setup a snapshot replication scenario, installing SqlExpress w/ Advance Tools on the subscriber machine.

We install our offline viewer windows smart client application on the subscriber, and are able to bring in a view of the needed data. However, we need this view to be available offline, for use when the prefferred application is unavailable or when the network is down. At this point, if the network is down our replicated db is not available either. So, I'm lost with the way I've got it working now. I'm not sure if it is a setup issue or if I've misunderstood how replication works. At any rate, our need appears to be similar in scope to yours. I'll check back here, and on my post to update the status.

Right now, we are examining our setup of the replication subscription and whether there is a way to achieve the goal desired, or if we have to employ a bulk copy insert into a local database for our subscriber downtime usage.

|||

Hi,

You might want to talk to us about a product that we sell (WANSync) which provides real-time asynchronous data replication, full tree replication topologies to protect from server and site failures. Should an SQL database server fail for any reason, a geographically remote SQL replica takes it's place and will allow you to keep working.

If you want more information or want to trial this solution for free, please email me at paul.maziere@.dataplex-systems.com

Regards, Paul.

Replicating Sql Server to Express Edition as backup application

Hello!

We are running a business critical client-server application that needs to have high availability to the end user.
I was wondering if it would be possible to setup a replication/data transfer from an existing Sql Server 7.0/8.0/9.0 (regular online environment running on server) TO an instance of Sql 2005 Express Edition (backup env. running on klient PC).
In case of server failure the application would redirect - accessing the local PC Express edition.

Does anyone have any input on this, and if it would be a possible alternative to use as extra standby- system. ?

Kind regards
TomasYes this is possible but there are certain exceptions.
And it depends on what kind of replication technology you are looking at.
SQL Server 2005 Books Online has more information on supported topologies.

Search for "Using Multiple Versions of SQL Server in a Replication Topology"|||

Hi Tomas.

It would appear that I have a similar type of need. See this post http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=677662&SiteID=1 which describes my situation. If you've got any further info on how this is achieved please respond. I'll do the same. We were able to create the windows form app and use Sql2005 Std to maintain a 'gold' standard db on our publisher/distributor machine. We have to replace our db daily with an entirely new dataset that is sent to us via a foreign host. We take that data an bulk copy it into our db. Then, we setup a snapshot replication scenario, installing SqlExpress w/ Advance Tools on the subscriber machine.

We install our offline viewer windows smart client application on the subscriber, and are able to bring in a view of the needed data. However, we need this view to be available offline, for use when the prefferred application is unavailable or when the network is down. At this point, if the network is down our replicated db is not available either. So, I'm lost with the way I've got it working now. I'm not sure if it is a setup issue or if I've misunderstood how replication works. At any rate, our need appears to be similar in scope to yours. I'll check back here, and on my post to update the status.

Right now, we are examining our setup of the replication subscription and whether there is a way to achieve the goal desired, or if we have to employ a bulk copy insert into a local database for our subscriber downtime usage.

|||

Hi,

You might want to talk to us about a product that we sell (WANSync) which provides real-time asynchronous data replication, full tree replication topologies to protect from server and site failures. Should an SQL database server fail for any reason, a geographically remote SQL replica takes it's place and will allow you to keep working.

If you want more information or want to trial this solution for free, please email me at paul.maziere@.dataplex-systems.com

Regards, Paul.

Replicating roles

Hello,

I use a merge replication between Sql Server and Sql Server Express.

When I enable a DB for .NET features (eg RoleManager), I have new tables and roles that are created and some GRANT are given on SPs.

When I replicate these DB to another one, none of my roles are replicated and I also loose my roles. Is there a way to replicate also the roles and the permissions ?

Thanks

Pierre-Emmanuel Dautreppe

use a postsnapshot script for this. if you deployed your subscription through a file copy (unc), you could package up the permissions in a script and use sp_addscriptexec to replicate this to all of your subscribers.