Replication error with sqlserver mobile:A request to send data to the computer running IIS is fa

I have smilar kind of an issue with replication. I had sucessfully done replication with Sqlce2.0 on sql server 2000. In development machine I had VS 2003, sqlce development tools.

Now I use the same code done in VS 2003 into VS2005, it sucessfully converted the code.

In server machine (win 2003) I installed sql server 2000, sql server 2000 service pack 4, SP4 merge replication components, sql server 2005 mobile server tools and .Net framework 2.0. Created pubication sucessfuly. In this machine I configured IIS as per the web synchronization wizard. Gave anyonymous permissions. Virual direcory is created sucessfully. I tested the server agent in IE http://myservername/aliasname/sqlcesa30.dll.

SQL Server Mobile Server Agent 3.0 is shown

My application opened successfuly in windows mobile 5.0 Pocket PC emulator. When try to sync its dislays error "A request to send data to the computer running IIS is failed, see Hrresult"

No firewall in both development and server machines.

The same code works if its sqlce20 perfectly with vs2003 code. Not in this

Can anyone tell me whats wrong in this?

Regards

Arif

I have moved this to the SQL Mobile forum for someone in the SQL Mobile team to look at.

Thanks

Amit

|||

Hello All,

It worked for me. I read some of the messages in this forum and found that I need to connect the Windows Mobile PPC emulator using activesync. I did it and now its working fine.

I was now able to do sync with both PPC2003 on Sql server 2000 and sqlce20 (VS2003 environment)

AND also

Windows mobile 5 on Sql Server 2000, SQL Server SP4, SP4 replication components, Sql server mobile (VS2005) succesfuly

Thanks for the questions and responses in this forum

Arif

www.anteriorsoft.com

|||

Thanks a lot for your compliments!

Laxmi Narsimha Rao ORUGANTI, MSFT, SQL Mobile, Microsoft Corporation

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 MSDE and SQL Server 2000

I got a corporate machine has SQL Server 2000 installed. And a laptop has
MSDE installed. Is this complicated to setup a 2 way replication in SQL
Server 2000 Enterprise Manager?
Not at all. The MSDE can't be set up as a transactional publisher, and most
people set up the MSDE as a subscriber because of the topology they're using
anyway. Apart from that it's pretty straightforward. Configuration of MSDE
on a separate bix when you can't connect to it using EM can be more
difficult though.
Cheers,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)
|||Use merge replication for bi-directional replication. Merge also works with
MSDE.
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
"Man Utd" <alanpltseNOSPAM@.yahoo.com.au> wrote in message
news:%23decwk1FGHA.376@.TK2MSFTNGP12.phx.gbl...
>I got a corporate machine has SQL Server 2000 installed. And a laptop has
> MSDE installed. Is this complicated to setup a 2 way replication in SQL
> Server 2000 Enterprise Manager?
>
|||Hi Hilary,
Could you tell me where can I get the detailed steps to set up the
replication process between the SQL Server 2000 and the laptop MSDE ?
As I am investigating the database to do this project, MSDE is an option,
and Firebird is another but I can only find some trial version of components
which have some limitations.
The reason why I need to do the replication is the sales persons bring the
laptop on site and then back to office hook up to the corporate sever
database and the replication can be done on demand or by schedule. So it
depends on if I can experiment that SQL Server 2000 and MSDE is a good
combination, the project will use this combination, otherwise, Firebird or
MySQL.
"Hilary Cotter" <hilary.cotter@.gmail.com> wrote in message
news:uFv4DO2FGHA.2320@.TK2MSFTNGP11.phx.gbl...
> Use merge replication for bi-directional replication. Merge also works
with
> MSDE.
> --
> 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
> "Man Utd" <alanpltseNOSPAM@.yahoo.com.au> wrote in message
> news:%23decwk1FGHA.376@.TK2MSFTNGP12.phx.gbl...
>

Replication between 64-bit and 32-bit?

We have a 32-bit edition today and want to secure the uptime by adding a cold
standby.
We want to purchase a new 64-bit machine with the 64-bit editions of OS/SQL.
The 64-bit should replicate data to our "old" 32-bit machine.
I have not found any information on MS-site about this, is this possible?
Will it work just to the same way as replicating between two 32-bit
enivironments?
You should be able to replicate between 32 bit and 64 bit SQL Server
editions. I have a scenario where distributor is 64 bit and publisher and
subscriber are 32 bit. It is working fine, and is transparent.
HTH,
Vyas, MVP (SQL Server)
SQL Server Articles and Code Samples @. http://vyaskn.tripod.com/
"Patrik" <Patrik@.nospam.nospam> wrote in message
news:4F9BA96C-F9AA-4C6E-BD30-391CD75F666A@.microsoft.com...
We have a 32-bit edition today and want to secure the uptime by adding a
cold
standby.
We want to purchase a new 64-bit machine with the 64-bit editions of OS/SQL.
The 64-bit should replicate data to our "old" 32-bit machine.
I have not found any information on MS-site about this, is this possible?
Will it work just to the same way as replicating between two 32-bit
enivironments?
|||Hello,
I suggest that you refer to the following information:
Features Supported by the Editions of SQL Server 2000 (64-bit)
http://msdn.microsoft.com/library/de...us/sql64/in_pr
eparing64_6184.asp
You can refer to the "Replication Features Supported by the Editions of SQL
Server 2000 (64-bit)" section.
advantages of a 64-Bit Environment :
http://www.microsoft.com/sql/64bit/p...Advantages.asp
Replication
The Replication features of SQL Server 2000 (64-bit) are nearly identical
to the 32-bit version, with the following features being supported:
"Snapshot Replication
"Transactional Replication
"Merge Replication
"Immediately updating subscribers
"Queued updating subscribers
However, there are a few special cases:
"As the Microsoft Jet engine is not supported, Microsoft Jet push
subscriptions for merge replication are not supported.
"Unless the subscriber provides a 64-bit ODBC or OLE DB driver,
transactional or snapshot push subscriptions for ODBC or OLE DB subscribers
are not supported.
"Because of the unavailability of 64-bit Data Transformation Services
(DTS), transformable push subscriptions are not supported.
In addition, the 64-bit versions of Windows Server 2003, Enterprise Edition
and Windows Server 2003, Datacenter Edition do not include certain features
that are included in the 32-bit versions of those operating systems.
These features are not included because of underlying differences between
the 32-bit and 64-bit architectures or because the features are not
appropriate in the environments where the 64-bit versions of Windows Server
2003, Enterprise Edition and Windows Server 2003, Datacenter Edition are
deployed.
For a complete list of differences, see "Differences Between 64-bit and
32-bit Releases (64-bit)" in SQL Server 2000 (64-bit) Books Online and
"Features unavailable on 64-bit versions of the Windows Server 2003 family"

Replication between 64-bit and 32-bit?

We have a 32-bit edition today and want to secure the uptime by adding a col
d
standby.
We want to purchase a new 64-bit machine with the 64-bit editions of OS/SQL.
The 64-bit should replicate data to our "old" 32-bit machine.
I have not found any information on MS-site about this, is this possible?
Will it work just to the same way as replicating between two 32-bit
enivironments?You should be able to replicate between 32 bit and 64 bit SQL Server
editions. I have a scenario where distributor is 64 bit and publisher and
subscriber are 32 bit. It is working fine, and is transparent.
--
HTH,
Vyas, MVP (SQL Server)
SQL Server Articles and Code Samples @. http://vyaskn.tripod.com/
"Patrik" <Patrik@.nospam.nospam> wrote in message
news:4F9BA96C-F9AA-4C6E-BD30-391CD75F666A@.microsoft.com...
We have a 32-bit edition today and want to secure the uptime by adding a
cold
standby.
We want to purchase a new 64-bit machine with the 64-bit editions of OS/SQL.
The 64-bit should replicate data to our "old" 32-bit machine.
I have not found any information on MS-site about this, is this possible?
Will it work just to the same way as replicating between two 32-bit
enivironments?|||Hello,
I suggest that you refer to the following information:
Features Supported by the Editions of SQL Server 2000 (64-bit)
http://msdn.microsoft.com/library/d...-us/sql64/in_pr
eparing64_6184.asp
You can refer to the "Replication Features Supported by the Editions of SQL
Server 2000 (64-bit)" section.
advantages of a 64-Bit Environment :
http://www.microsoft.com/sql/64bit/...tAdvantages.asp
Replication
The Replication features of SQL Server 2000 (64-bit) are nearly identical
to the 32-bit version, with the following features being supported:
" Snapshot Replication
" Transactional Replication
" Merge Replication
" Immediately updating subscribers
" Queued updating subscribers
However, there are a few special cases:
" As the Microsoft Jet engine is not supported, Microsoft Jet push
subscriptions for merge replication are not supported.
" Unless the subscriber provides a 64-bit ODBC or OLE DB driver,
transactional or snapshot push subscriptions for ODBC or OLE DB subscribers
are not supported.
" Because of the unavailability of 64-bit Data Transformation Services
(DTS), transformable push subscriptions are not supported.
In addition, the 64-bit versions of Windows Server 2003, Enterprise Edition
and Windows Server 2003, Datacenter Edition do not include certain features
that are included in the 32-bit versions of those operating systems.
These features are not included because of underlying differences between
the 32-bit and 64-bit architectures or because the features are not
appropriate in the environments where the 64-bit versions of Windows Server
2003, Enterprise Edition and Windows Server 2003, Datacenter Edition are
deployed.
For a complete list of differences, see "Differences Between 64-bit and
32-bit Releases (64-bit)" in SQL Server 2000 (64-bit) Books Online and
"Features unavailable on 64-bit versions of the Windows Server 2003 family"

Replication between 64-bit and 32-bit?

We have a 32-bit edition today and want to secure the uptime by adding a cold
standby.
We want to purchase a new 64-bit machine with the 64-bit editions of OS/SQL.
The 64-bit should replicate data to our "old" 32-bit machine.
I have not found any information on MS-site about this, is this possible?
Will it work just to the same way as replicating between two 32-bit
enivironments?You should be able to replicate between 32 bit and 64 bit SQL Server
editions. I have a scenario where distributor is 64 bit and publisher and
subscriber are 32 bit. It is working fine, and is transparent.
--
HTH,
Vyas, MVP (SQL Server)
SQL Server Articles and Code Samples @. http://vyaskn.tripod.com/
"Patrik" <Patrik@.nospam.nospam> wrote in message
news:4F9BA96C-F9AA-4C6E-BD30-391CD75F666A@.microsoft.com...
We have a 32-bit edition today and want to secure the uptime by adding a
cold
standby.
We want to purchase a new 64-bit machine with the 64-bit editions of OS/SQL.
The 64-bit should replicate data to our "old" 32-bit machine.
I have not found any information on MS-site about this, is this possible?
Will it work just to the same way as replicating between two 32-bit
enivironments?|||Hello,
I suggest that you refer to the following information:
Features Supported by the Editions of SQL Server 2000 (64-bit)
http://msdn.microsoft.com/library/default.asp?url=/library/en-us/sql64/in_pr
eparing64_6184.asp
You can refer to the "Replication Features Supported by the Editions of SQL
Server 2000 (64-bit)" section.
advantages of a 64-Bit Environment :
http://www.microsoft.com/sql/64bit/productinfo/SQL64bitAdvantages.asp
--
Replication
The Replication features of SQL Server 2000 (64-bit) are nearly identical
to the 32-bit version, with the following features being supported:
" Snapshot Replication
" Transactional Replication
" Merge Replication
" Immediately updating subscribers
" Queued updating subscribers
However, there are a few special cases:
" As the Microsoft Jet engine is not supported, Microsoft Jet push
subscriptions for merge replication are not supported.
" Unless the subscriber provides a 64-bit ODBC or OLE DB driver,
transactional or snapshot push subscriptions for ODBC or OLE DB subscribers
are not supported.
" Because of the unavailability of 64-bit Data Transformation Services
(DTS), transformable push subscriptions are not supported.
In addition, the 64-bit versions of Windows Server 2003, Enterprise Edition
and Windows Server 2003, Datacenter Edition do not include certain features
that are included in the 32-bit versions of those operating systems.
These features are not included because of underlying differences between
the 32-bit and 64-bit architectures or because the features are not
appropriate in the environments where the 64-bit versions of Windows Server
2003, Enterprise Edition and Windows Server 2003, Datacenter Edition are
deployed.
For a complete list of differences, see "Differences Between 64-bit and
32-bit Releases (64-bit)" in SQL Server 2000 (64-bit) Books Online and
"Features unavailable on 64-bit versions of the Windows Server 2003 family"sql

replication and data move

Hi,
I'm planning to move MS SQL Server 2000 instance to another server. I know
that the easiest way is to copy data directory from one machine to another
and set new server name to the old one. Because of some reasons I can't do
it in thisy way. Besides that I don't watn to move all databases but some of
them. Unfortunately, some of these databases are replicated (part of them is
published and another part is subscibed).
How to move MSSQL instance to another machine keeping replication working
properly without starting replication from scratch? Is there way to restore
database (published or subscribed) with already set replication?
Thanks
Marcin> Hi,
> I'm planning to move MS SQL Server 2000 instance to another server. I know
> that the easiest way is to copy data directory from one machine to another
> and set new server name to the old one. Because of some reasons I can't do
> it in thisy way. Besides that I don't watn to move all databases but some
of
> them. Unfortunately, some of these databases are replicated (part of them
is
> published and another part is subscibed).
> How to move MSSQL instance to another machine keeping replication working
> properly without starting replication from scratch? Is there way to
restore
> database (published or subscribed) with already set replication?
> Thanks
> Marcin
--
You can't do it. According to SQL Server Books Online:
Restoring Backups of Replicated Databases to a Different Server or Database
When you restore a backup of a replicated database to a server or database
other than the one on which it was created, your replication settings
cannot be preserved. For publishing databases and merge subscribing
databases, a full restore of the database and logs is followed by an
automatic removal of replication meta data from the database when the
database or server you restore to differs from the one on which the backup
was created.
Hope this helps,
--
Eric Cárdenas
Senior support professional
This posting is provided "AS IS" with no warranties, and confers no rights.

replication and data move

Hi,
I'm planning to move MS SQL Server 2000 instance to another server. I know
that the easiest way is to copy data directory from one machine to another
and set new server name to the old one. Because of some reasons I can't do
it in thisy way. Besides that I don't watn to move all databases but some of
them. Unfortunately, some of these databases are replicated (part of them is
published and another part is subscibed).
How to move MSSQL instance to another machine keeping replication working
properly without starting replication from scratch? Is there way to restore
database (published or subscribed) with already set replication?
Thanks
Marcin
> Hi,
> I'm planning to move MS SQL Server 2000 instance to another server. I know
> that the easiest way is to copy data directory from one machine to another
> and set new server name to the old one. Because of some reasons I can't do
> it in thisy way. Besides that I don't watn to move all databases but some
of
> them. Unfortunately, some of these databases are replicated (part of them
is
> published and another part is subscibed).
> How to move MSSQL instance to another machine keeping replication working
> properly without starting replication from scratch? Is there way to
restore
> database (published or subscribed) with already set replication?
> Thanks
> Marcin
You can't do it. According to SQL Server Books Online:
Restoring Backups of Replicated Databases to a Different Server or Database
When you restore a backup of a replicated database to a server or database
other than the one on which it was created, your replication settings
cannot be preserved. For publishing databases and merge subscribing
databases, a full restore of the database and logs is followed by an
automatic removal of replication meta data from the database when the
database or server you restore to differs from the one on which the backup
was created.
Hope this helps,
Eric Crdenas
Senior support professional
This posting is provided "AS IS" with no warranties, and confers no rights.

replication and data move

Hi,
I'm planning to move MS SQL Server 2000 instance to another server. I know
that the easiest way is to copy data directory from one machine to another
and set new server name to the old one. Because of some reasons I can't do
it in thisy way. Besides that I don't watn to move all databases but some of
them. Unfortunately, some of these databases are replicated (part of them is
published and another part is subscibed).
How to move MSSQL instance to another machine keeping replication working
properly without starting replication from scratch? Is there way to restore
database (published or subscribed) with already set replication?
Thanks
Marcin> Hi,
> I'm planning to move MS SQL Server 2000 instance to another server. I know
> that the easiest way is to copy data directory from one machine to another
> and set new server name to the old one. Because of some reasons I can't do
> it in thisy way. Besides that I don't watn to move all databases but some
of
> them. Unfortunately, some of these databases are replicated (part of them
is
> published and another part is subscibed).
> How to move MSSQL instance to another machine keeping replication working
> properly without starting replication from scratch? Is there way to
restore
> database (published or subscribed) with already set replication?
> Thanks
> Marcin
--
You can't do it. According to SQL Server Books Online:
Restoring Backups of Replicated Databases to a Different Server or Database
When you restore a backup of a replicated database to a server or database
other than the one on which it was created, your replication settings
cannot be preserved. For publishing databases and merge subscribing
databases, a full restore of the database and logs is followed by an
automatic removal of replication meta data from the database when the
database or server you restore to differs from the one on which the backup
was created.
Hope this helps,
Eric Crdenas
Senior support professional
This posting is provided "AS IS" with no warranties, and confers no rights.

Replication 2000 - What if Publisher dead

What if a Publication and Distribution server machine fail to work. Do I need to reinitiliaze the whole snapshot on a new machine and retransmit the data to the subscriber. Or can I make use of replication script to recreate the publication and distribution and then replicate to existing subscriber using same machine name?

ThanksHow bad did it fail?|||Let say, if unable to load the SCSI hardisk, or the hardware failured.
Thanks

Originally posted by joejcheng
How bad did it fail?

Replication ( Local to Hosting Company )

Hi,
I wanna replicate two SQL Server 2000 DB, On is in my Company behind a DSL
Router, the other is in a Machine on somewhere which I purchase as a Hosting
package..
Configuration of Local SQL Server is already Done by Me and Publication is
Created, I chose Snapshot one...
The problem is, How My remote SQL Server subscribe to the publisher, How can
I Subscribe and, If I can, How my Remote Server See my local Snapshot files
in order to get them in Remote DB, Should I send Snapshot files to Remote or
We have another solution ?
( Note that on Remote, I only can make a subscription, others are disabled )
What kind of solution do you propose ?
Have a look at this article: http://support.microsoft.com/?id=321822
Rgds,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)
|||Configure your publication for an anoymous pull. Configure your ftp site for
anonymous access, and configure your publication to create the snapshot
within the ftp site.
Configure the subscriber for replication and then pull the subscription from
the subscriber.
Hilary Cotter
Looking for a SQL Server replication book?
Now available for purchase at:
http://www.nwsu.com/0974973602.html
"BonGee" <Bongee@.bonbon.n.e.t> wrote in message
news:ufJsvNI3EHA.3336@.TK2MSFTNGP11.phx.gbl...
> Hi,
> I wanna replicate two SQL Server 2000 DB, On is in my Company behind a DSL
> Router, the other is in a Machine on somewhere which I purchase as a
> Hosting
> package..
> Configuration of Local SQL Server is already Done by Me and Publication is
> Created, I chose Snapshot one...
> The problem is, How My remote SQL Server subscribe to the publisher, How
> can
> I Subscribe and, If I can, How my Remote Server See my local Snapshot
> files
> in order to get them in Remote DB, Should I send Snapshot files to Remote
> or
> We have another solution ?
> ( Note that on Remote, I only can make a subscription, others are
> disabled )
> What kind of solution do you propose ?
>

Replication - DB2 as publisher - SQL 2005 as subscriber

I have been looking for a way to replicate data from a DB2 system running on an AIX machine. I found some information related to doing this with SQL2000, but not with 2005. Can this be done - preferably without writing our own provider.

Thanks in advance

I have the same problem. I am trying to replicate data from DB2/AS400 to SQL Server 2005. I am able to connect to DB2 through SQL Analyzer and can query DB2 tables but I don’t know how to replicate data. I have done my research and people told me that it can’t be done but couldn’t find any article or book (I also went to book store) which could tell me the way how to do it. If you find any thing please post it here.

Thanks

|||You have to use something like Data Mirror for this or code your own solution.|||But then what about Heterogeneous Replication. Is it just for Oracle to and from SQL Server?

Replication - DB2 as publisher - SQL 2005 as subscriber

I have been looking for a way to replicate data from a DB2 system running on an AIX machine. I found some information related to doing this with SQL2000, but not with 2005. Can this be done - preferably without writing our own provider.

Thanks in advance

I have the same problem. I am trying to replicate data from DB2/AS400 to SQL Server 2005. I am able to connect to DB2 through SQL Analyzer and can query DB2 tables but I don’t know how to replicate data. I have done my research and people told me that it can’t be done but couldn’t find any article or book (I also went to book store) which could tell me the way how to do it. If you find any thing please post it here.

Thanks

|||You have to use something like Data Mirror for this or code your own solution.|||But then what about Heterogeneous Replication. Is it just for Oracle to and from SQL Server?

Replication - DB2 as publisher - SQL 2005 as subscriber

I have been looking for a way to replicate data from a DB2 system running on an AIX machine. I found some information related to doing this with SQL2000, but not with 2005. Can this be done - preferably without writing our own provider.

Thanks in advance

I have the same problem. I am trying to replicate data from DB2/AS400 to SQL Server 2005. I am able to connect to DB2 through SQL Analyzer and can query DB2 tables but I don’t know how to replicate data. I have done my research and people told me that it can’t be done but couldn’t find any article or book (I also went to book store) which could tell me the way how to do it. If you find any thing please post it here.

Thanks

|||You have to use something like Data Mirror for this or code your own solution.|||But then what about Heterogeneous Replication. Is it just for Oracle to and from SQL Server?

Replication

I need to copy 10 Databases (150GB) to another SQL machine.
Now I need the destination machine to be updated every 24 hours.
Transcational replication is not helping me - cause it doesn't copy tables
without primary keys.
Snapshot replication is not helping me either - cause i can't transfer every
24 hours 150GB.
Help me please,
Aviad Avi.
You can use merge and configure it to only move the data one way. Add the
ExchangeType parameter to the merge agent with a value of 2.
Rand
This posting is provided "as is" with no warranties and confers no rights.
|||It seems you on something.
Can you please explain what do you meen by adding the ExchangeType parameter
with a value of 2?
Where should i configure the Merge?
"Rand Boyd [MSFT]" <rboyd@.onlinemicrosoft.com> wrote in message
news:QQXX4wl1EHA.768@.cpmsftngxa10.phx.gbl...
> You can use merge and configure it to only move the data one way. Add the
> ExchangeType parameter to the merge agent with a value of 2.
> Rand
> This posting is provided "as is" with no warranties and confers no rights.
>
|||Why does it called merge? because the uniqueidentifier colum that is added?
"Aviad Avi" <aviad00001@.yahoo.ca> wrote in message
news:%23RWGK1l1EHA.304@.TK2MSFTNGP11.phx.gbl...
> It seems you on something.
> Can you please explain what do you meen by adding the ExchangeType
parameter[vbcol=seagreen]
> with a value of 2?
> Where should i configure the Merge?
> "Rand Boyd [MSFT]" <rboyd@.onlinemicrosoft.com> wrote in message
> news:QQXX4wl1EHA.768@.cpmsftngxa10.phx.gbl...
the[vbcol=seagreen]
rights.
>
|||Moreover,
I think I need to run it with 1 value = push
don't I?
"Aviad Avi" <aviad00001@.yahoo.ca> wrote in message
news:%23RWGK1l1EHA.304@.TK2MSFTNGP11.phx.gbl...
> It seems you on something.
> Can you please explain what do you meen by adding the ExchangeType
parameter[vbcol=seagreen]
> with a value of 2?
> Where should i configure the Merge?
> "Rand Boyd [MSFT]" <rboyd@.onlinemicrosoft.com> wrote in message
> news:QQXX4wl1EHA.768@.cpmsftngxa10.phx.gbl...
the[vbcol=seagreen]
rights.
>
|||In the merge agent job, on the middle step, add -
ExchangeType 2 to the parameters list. This is one of
those cases where the parameter needs adding here rather
than to the profile. The values according to BOL are :
UPLOAD 1 Only merge Subscriber changes with the
Publisher.
DOWNLOAD 2 Only merge Publisher changes with the
Subscriber.
BIDIRECTIONAL 3 Merge all changes between the Publisher
and Subscriber (default).
Rgds,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)
|||Snapshot and Transactional in their plain forms are
essentially unidirectional. Merge is bidirectional, and
the subscriber can change data offline, so there is the
potential that data can conflict. However, in certain
configurations a change to a different column on the same
row is not treated as a conflict and the changes
are 'merged'.
HTH,
Paul Ibison SQL Server MVP, www.replicationanswers.com
(recommended sql server 2000 replication book:
http://www.nwsu.com/0974973602p.html)