SQLServerCentral / SQL Server 7,2000 / Replication

Replicating My SQL Server

vishvaain2005 — Wed, 24 Apr 2013 05:01:01 GMT

Dear All,I have to prepare a backup server for my SQL Server, which should be automatically updated as the changes in main server.I want to know can we do the same through Replication or by some other means.RegardsVishal Sharma

Initial snapshot for publication is not yet available

homebrew01 — Mon, 05 Feb 2007 23:07:00 GMT

I'm not sure why my transactional replication is giving me: "The initial snapshot for publication 'XYZ' is not yet available." I have 1 publication going to 3 subscribers on different servers. After creating new subscriptions on Subscriber #3, the subscriptions on Subscriber #1 stopped pulling new data (was running fine for months)

Does re-creating a snapshot at the publisher, to go to a new subscriber have an effect on my long running original subscription ??

I reinitialized the subscription on subscriber #1, re-ran the snapshot at the publisher, then when it finished, I re-ran the subscription pull job. at subscriber #1. It completes normally, but finishes in just a few seconds & does nothing. It seems I have to drop the subscription and re-create it.

Any thoughts

How can we achive the replica of databases for SQL SERVER?

hemantwithu — Wed, 06 Mar 2013 02:59:51 GMT

I have been working in VB6 to VB.NET migration project.In VB6 project they have individual databases(access db .mdb) for every user now we made that to Centralized database SQL SERVER.In VB6 the individual db is a replica DB and has a Master-db which located some where. Now we need to do this process for SQL SERVER also.How can we achieve this for Centralized database like SQL Server?This should work for each and every user also.Can anybody help regarding this or share any links ?

Pull to Push subscription

Rob Mahaney — Thu, 12 Jan 2006 14:36:00 GMT

OK I know I am dreaming but does anyone know of a way to switch a transactional subscription from Pull to Push without having to regenerate a snapshot? We have a 166 GB database that they want to change subscription type and I don't want to pull an all nighter dropping and adding the subscription.

The process could not bulk copy into table '"dbo"."

Sharon Kumar — Wed, 27 Feb 2013 06:04:10 GMT

This errors Message was found in the Job History.2013-02-27 12:28:18.758 Agent message code 20037. The process could not bulk copy into table 2013-02-27 12:28:18.838 Category:NULLSource: Microsoft SQL Server Native Client 11.0Number: Message: End of file reached, terminator missing or field data incomplete2013-02-27 12:28:18.838 Category:NULLSource: Number: 20253Message: To obtain an error file with details on the errors encountered when initializing the subscribing table, execute the bcp command that appears below. Consult the BOL for more information on the bcp utility and its supported options.2013-02-27 12:28:18.838 Category:NULLSource: Number: 20253Message: bcp "TestDB"."dbo"."ReportType" in "C:\Testing\ReplData\unc\xxxxxxxxxxxxxxxx\20130227175358\xxxxxxxxb227380_514.bcp" -e "errorfile" -t"<x$3>" -r"<,@g>" -m10000 -S SqlSrvB -T -wIn the Replication "Distributor to Subscriber History' Error messages:The process could not bulk copy into table '"dbo"."ReportType"'. (Source: MSSQL_REPL, Error number: MSSQL_REPL20037)Get help: http://help/MSSQL_REPL20037End of file reached, terminator missing or field data incompleteTo obtain an error file with details on the errors encountered when initializing the subscribing table, execute the bcp command that appears below. Consult the BOL for more information on the bcp utility and its supported options. (Source: MSSQLServer, Error number: 20253)Get help: http://help/20253 bcp "TestDB"."dbo"."ReportType" in "C:\Testing\ReplData\unc\xxxxxxxxxxxxxxxx\20130227175358\xxxxxxxxb227380_514.bcp" -e "errorfile" -t"<x$3>" -r"<,@g>" -m10000 -S SqlSrvB -T -w (Source: MSSQLServer, Error number: 20253)Get help: http://help/20253When Ran the BCP in Command Prompt I got Starting Copy.....0 Rows Copied.Bother are Sql Server 2012 servers In my table one of the column dataype is timestamp and the schema structure is same on the both publisher and subscriber instances. I hope in the BCP Files there is data but it not able to load data.Please help me to resolve this issue.I appreciate your help.. Thanks

SQL Server 2005 Replication between Disconnected Sites

David-478183 — Sun, 11 May 2008 22:35:42 GMT

We have a database application that we want to run on two (and possibly more) different servers that will not be able to be connected. Is there a way to use (and set up) replication in SQL Server 2005 to periodically synchronise the data between these two databases?Thanks,David

About moving data between databases

mpradeep23 — Tue, 22 Jan 2013 02:20:17 GMT

I have few tables that needed to be replicated/synchronized across several databases in our SQL Server 2012 .Example:DB1 has T1, T2 and T3 - these are constantly being updated by the application, APP1 running on DB1.DB2 needs to have an updated copy of T1 at all times, also, there is a different application, APP2 runs only on DB2.Both DB1 and DB2 are located on the different instance.Would it be possible to replicate T1, T2 and T3 from DB1 to DB2 ?thanks with best regardspradeep

about Transanctional Replication

mpradeep23 — Mon, 21 Jan 2013 23:49:00 GMT

hi can we have transcational replication for only few tables thanks with best reagrdspradeep

Cannot drop the database XXX because it is being used for replication.

e.francone — Tue, 11 May 2004 04:46:00 GMT

When I try to drop the XXX database SQLServer returns me this error message:

Server: Msg 3724, Level 16, State 3, Line 1Cannot drop the database XXX because it is being used for replication.

I've also tried to execute the following code but nothing has changed.

exec sp_removedbreplication 'XXX'goexec sp_dboption 'XXX','published',falsegoexec sp_dboption 'XXX','merge publish',falsego

The XXX DB is a restore of "Distribution" database of a Production Server that is a publication server!

Someone can help me?

Thanks for all suggestions!!!

Frank

SQL 2008 R2 Replication help

smiller 94226 — Tue, 01 Jan 2013 06:35:48 GMT

We have two separate production db servers whose only difference is data content. We are trying to publish the data from each server to a single separate distribution server (separate distrib dbs) and then replicate all the data to tables named by server on a third remote subscriber box.We were successful at setting up the first distributor, publication and subscription using t-rep. However, when setting up the second server publication and subscription the new one is taking over and the first one stops running.What am I doing wrong?

The subscription(s) have been marked inactive.....

jmittmann — Tue, 11 Jan 2005 05:03:00 GMT

Hallo,

from time to time my transactional (push) replications on SQL2000 SP3a servers send me the following error message:

Error Message : The subscription(s) have been marked inactive and must be reinitialized. NoSync subscriptions will need to be dropped and recreated.Error Detail : The subscription(s) have been marked inactive and must be reinitialized. NoSync subscriptions will need to be dropped and recreated. (Source: Server Name (Data source); Error number: 21074)

My subscriptions have been very active for at least 2 years and in the properties "Subscriptions never expire" is marked.

I know that I can restart replication by setting the status column in distribution..MSsubscriptions to 2 but can anyone tell me why this problem occurs and how I can prevent it in future?

Thank you for your help

Cleaning up Replication Monitor

Chris Wasser — Mon, 12 Jul 2004 15:00:00 GMT

I have sucessfully removed an old publication and it subscriptions, but I am still seeing references to it in the Replication Monitor under Publishers, Snapshot Agents, and Distribution Agents. When I try to delete the listing under Publishers I get an error message that states the following:Error 21776:[SQL-DMO] The name 'Publication1' was not found in the TransPublications collection. If the name is a qualified name, use{} to separate various parts of the name and try again.When I try to look at the properties of the agents I get the following error message:Error 14262: The specified @job_id('xxxyyyzzz') does not exist.So it appears that the old publication and its components are in fact gone (or at least to SQL Server they cannot be found), but these error messages are still there and I cannot remove them. While this is not affecting any functionality, it "looks" like something is wrong when viewed through SQL-EM.I am using SQL_EM to manage these replication services, but can run procs through Query Analyzer if that will help.Any help or direction would be greatly appreciated.-Chris

Trans Replication Snapshot not getting applied to Subscriber database

Hemant Korde — Fri, 16 Nov 2012 10:07:52 GMT

here is a situation I am facing and unable to find answer thus far:I have created a trans replication (SQL Server 2005) from server A to B with just 1 article ( table with over 4 million rows). Publisher is going to just one subscriber (also 2005). After creating Publication and subscription the status isSnapshot Agent generated and created a snapshot folder with data in Repldata.Log Reader agent is runningDistributor is showing synchronization in progress and following message:The concurrent snapshot for publication 'apiTransLog To 100.60' is not available because it has not been fully generated or the Log Reader Agent is not running to activate it. If generation of the concurrent snapshot was interrupted, the Snapshot Agent foThis snapshot is not getting applied to the subscriber DB. What is wrong and what is the solution? I tried removing and recreating same replication twice but getting same results.Please help.Thanks.HK

Transactional Replication - Snapshot is not getting applied to subscriber

Hemant Korde — Thu, 15 Nov 2012 05:34:13 GMT

Need Help:I have looked everywhere but I cannot find help for this specific topic. Any help to pinpoint the problem and how to fix it will be highly appreciated:We are running SQL Server 2005. I have created a trans replication on a single subscriber. Both servers are in the same network (no MPLS required for data transfer). When I looked at the snapshot agent, it shows sucessfully completed status. I can also see the snapshot folder. Logreader is running and shows number of articles transferred. Distributor shows it is running sfor over 9 hours since I initially created the replication. However, nothing is getting applied to the subscriber.Can anyone gone through the same problem, list out what I need to check and how to fix this problem. I am unable to find exact answer anywhere on the internet.Thanks.HK

Replications not showing in monitor

Marts — Tue, 29 May 2012 14:00:19 GMT

I have a new issue that is completely confounding me.The IT guy prepared a VM image of our old sql server 2000 machine in preperation for migration to sql server 2012.However as part of the evaluation, I needed to get rid of the replication on this VM, as it was messing up the production machine.Stupidly enough, I just went ahead and deleted the push subscriptions from the machine, without thinking that it would screw the production machine.I managed to get into a state where the production machine is seemingly pushing data out (transaction and merge) to the various places it needs to, but they do not show in the replication monitor now at all. Additionally, I cannot delete, re-initialize or anything with the processes...Any ideas to help would be greatly appreciated.Martin

Enable Oracle Subscription for MSSQL Publisher

amit.kini — Sun, 04 Nov 2012 23:29:24 GMT

We have a MS SQL DB server for Cricket DB .The requirement is to Enable a Oracle Subscription for a sql server Publisher on our cricket DB, so that we can send live updates in real time.I am facing an issue while configuring the subscription.This is what I have tried:1. Configured a sql server publication with articles2. Tried to configure an Oracle subscriber to publication configured in step 1 but seems like the Data source Name is not being recognized by the sql server.It does say the subscription is configured but it gives error while initializing the snapshot.Any idea on what could be going wrong here?Also, one issue here is, I think it looks for TNSNAMES.ORA file for the data source name that I provide. I have sql developer as the oracle client and I don’t connect using the TNS name.In this case where do I need to place the TNSNAMES.ora file? Any thoughts on this would be appreciated. Also if you are aware of any alternate way to approach this it would be helpful. Please advise.

injection attack

saeed_edp — Wed, 02 Jul 2008 05:03:28 GMT

Pleas help me!I'm under injection attack and i don't no what can i do.This script ' script src=http://www.hdadwcd.com/b.js /script' is injected to may database (sql server 2000).It not only injected in many of databases field but also renamed my publication name to : " [b]publication name[/b] script src=http://www.hdadwcd.com/b.js /script "How can i repair it and stop this injectionHow can I edit binary fields in MSrepl_commands and delete this script from command field.

Job Suspended - WHY???

jlerman — Fri, 22 Nov 2002 17:44:00 GMT

Why would a push subscription job be suspended immediately after I create it?I just don't understand - boo hoo!Thanksjulie

transactional replication subscription deleted automatically SQL SERVER 2000

bando — Thu, 30 Aug 2012 03:01:35 GMT

I have replicated(transactional replication) databases in sql server2000. it had some scheduled time for doing replication. but after few days i saw that the subscription task had disappeared without any cause. so again I subscribed the publication but after one day same problem occurred!! again deleted..I dont know why..please give me a solution for this.Thank you.

How to run snapshot agent automatically

shohelr2003 — Tue, 02 Oct 2012 00:30:28 GMT

Hi Experts,I have done successfully snapshot replication. But I have to start snapshot agent manually. After manually starting, replication from distributor to subscriber has done.Now I want to start snapshot agent automatically in distributor server. Please help me. Thanks in advance.Regards,Rana

Transactional Replication

Dennis-214270 — Mon, 01 Oct 2012 07:46:37 GMT

SQL Server 2000 I have a table being replicated named owner.MyTable on the Source DB and dbo.MyTable on the Destination DB. Do I have go through drop_subscription ...drop_Article ...Add_article ...Add-Subscription ..EXEC sp_refreshsubscriptions SNAPSHOTor can I just do a new Add_Subscription and have the owner.MyTable Database published as owner.MyTable AND db.MYTable?

Unable to replicate in SQL Server 2000 using Transactional Replication

shohelr2003 — Thu, 27 Sep 2012 00:40:20 GMT

1. My database consists of 397 tables. Platform is SQL Server 2000 Enterprise Edition2. While creating a publication using transactional replication, I get most of the tables are crossed mark. So I can not select required tables. But if I use snapshot replication, there is no such problem. I can select all of the tables. I am not getting the reason. Please let me know where is the problem.

log reader agent stuck in 'retrying'

Dennis-214270 — Sat, 22 Sep 2012 08:29:14 GMT

trying to set up a simple publication on sql server 2000 (Microsoft SQL Server 2000 - 8.00.2039) My SQL Agent is running using an NT authenticated account that is an administrator on the server. I created a new Publication of 2 tables - set it up as transactional replication - continuous log reading. I basically took all of the defaults in the wizard. The log reader job starts - then bounces from starting to retrying for 15 mins or so before failing. I do not see any errors in the sql server or replication log. The only error I can find is in the application event log for the job itself: SubSystem Message - Job 'TestDB-TestDB-8' (0x64C7317E150D984198AA5473511F6558), step 2 - Server execution failedcan anyone help????

Bulk_logged mode during reinitialization - sql server 2000 transactional RePL

Jpotucek — Wed, 19 Sep 2012 08:50:50 GMT

Running a reinitialization of one of my Subscribers (SQL Server 2000 Transactional replication)The bulk-inserts are giving me grief - we have limited space. I changed the recovery mode of the subscriber DB to bulk-logged and I am doing FREQUENT transaction log backups. I read that the entire process is one long transaction - but I think that means one transaction for each article? So I should be able to shrink the log between larege tables??????

subscriber''s records disappear with merge replication

David Poluxt — Tue, 24 Jan 2006 14:51:00 GMT

Hello everyone,

I am struggling with getting a merge replication working. On the publisher, I have an empty table. The subscriber has a table of the exact same structure, with 1 record. When I engage a subscription, instead of the seeing the 1 record go up to the publisher, the subscription instead wipes out the record on the subscriber! Obviously, this is not the way merge is supposed to work, and it must be something simple I'm doing wrong. Thanks in advance for any help!

Replicate many databases to central server

Lenny Miranda Matos — Thu, 02 Aug 2012 19:38:23 GMT

Hello, I want to replicate many (almost 50) (published) databases to central (subscriber) server. Published databases are similar, not equal, but there isn´t in these databases any duplicated table name and subscriber server will be accesed from web.My preocupation is about the bandwidth in the server. What is better replicate 50 databases to 50 central databases or 50 databases to 1 central big database with all needed tables, views, procedures and functions from 50 published databases...?Thanks in advance ...Lenny

The subscription(s) have been marked inactive and must be reinitialized. NoSync subscriptions will need to be dropped and recreated. The step failed.

Krasavita — Thu, 21 Jun 2012 08:11:34 GMT

Hello,I get this error,what do I need to do, please help me Thank youThe subscription(s) have been marked inactive and must be reinitialized. NoSync subscriptions will need to be dropped and recreated. The step failed.

auto_initialization_policy

psteja2000 — Fri, 27 Jul 2012 16:18:54 GMT

Scenario:Merge ReplicationSQLServer 2008 R2 PulisherSQLServer 2008 Express Subscriber (Pull)Web Synchronizationpublication property auto_initialization_policy is set to 1.publication property replicate_ddl is set to 0.Snapshot recreated and publication marked for reinitialization on next sync.After snapshot created and before sync happens, I delete a couple of rows from the article (publication side). These rows exist already on subscriber side because of previous syncs.Now I sync on the subscriber side. After sync, I do not see the deleted rows on both sides. Can anyone please explain why?? data is synched before snapshot is applied right? so rows are deleted while sync and snapshot is applied after. Snapshot has the deleted rows in it because rows are deleted after snapshot creation. So why don't show up on both sides in the end?

use exchange type to achieve upload only

psteja2000 — Fri, 27 Jul 2012 16:07:08 GMT

in a merge replication scenario with pull subscriptions using web synchronization, like we have download only articles, is there a way to achieve upload articles?. We have some articles which are always subscriber to publisher. I read online somewhere (can't locate it again) that web synchronization doesn't support upload only. I also read somewhere that if we put a filter like 'where 1=0), that will stop down flow. But can anyone please comment on if such a filter really improves performance? As opposed to leaving it bidirectional.

same article in multiple publications

psteja2000 — Fri, 20 Jul 2012 08:27:58 GMT

Posted this elsewhere too but this is a generic topic so reposting:We have a merge replication(2008R2) scenario with pull subscriptions. Currently there is only one publication but we are adding a new publication, where some articles are going ot be common. Some of the common articles are going to be download only. but some are updateable on both sides. With this information, can someone please point me the right direction to achieve this? Obvious goal is to do it right the first time even if the solution seems eccentric. Thank you.

Replication Error

sqlstar2011 — Fri, 08 Dec 2006 05:39:00 GMT

I am running replication from a clustered sql server to an instance of sql on a diff. box. When I performed failover on the source cluster replication broke. Publisher seems to work fine. However on the subscriber I get following error message:

Invalid object name 'tempdb.dbo.MSdistributor_access'. The step failed.

any idea how to troubleshoot this? Seems like there is not much on this online.

Thanks

How to fix corrupted index on subscriber table

sanny bae — Thu, 04 Aug 2005 14:34:00 GMT

Hi there,

My company uses MS Merge Replication in replicating data across different cities.

Here's the merge replication model:Site A: (merge replication) - 4 servers - A1, A2, A3, A4 - A1 is the publisher - A2, A3, A4 subscribe to A1

Site B: (merge replication) - 3 servers - B1, B2, B3 - B1 is the publisher for site B. - B1 also subscribes to A1, in order to get Site A's data. - B2 and B3 subscribe to B1

All servers on Site A and Site B generate data, and the data generated needs to be replicated all over to the other servers.

An index of a user table on A2 (first subscriber) is corrupted. The database size is 20GB, and this corrupted table has over 5 million rows.

The system is live and we can't afford to lose any data. We also don't have a test system in place where we could test. This is what I have in mind, can you tell me if this is sufficient to fix the problem?

- Shut down merge agent and SQL server on A2.- Disable merge agent on A1 so it won't write to A2.- Start up SQL server alone on A2.- Make it single user mode for this database.- DBCC DBREINDEX on corrupted table.- Remove single user mode.- Enable merge agent on A1.- Restart SQL server on A2.

Please help.

Thanks in advance,baes

SQLserver time out expire

ashu_77in 23221 — Fri, 06 Jul 2012 11:55:07 GMT

Dear forums,I have facing one problem on my application. I am fetching my record from my application (front end is VB)but its throw sql servererror - TIME OUT EXPIRE...I have checked query and connection . but every thing is ok . I am facing this problem is last 2 days.when i stop the sqlserver services and then restart my problem resolved only some time.after that its show same error msg.I also checked the data file and logfile. i found that my log file size is increase day by day . please give me the solution ASAP.Thanks Ashish

set a field to null

giorgiochiappetta — Wed, 04 Jul 2012 08:59:46 GMT

I have a replication between two servers. It works well. But I want to set to null some fields in a table of the subscriber. I tried to change the trigger [dbo]. [Sp_MSins_ but that is regenerated every Reinitialize the replica. How can I do? thanks

Replication error " A required Previleage not held by the client"

Rajo — Mon, 18 Jun 2012 01:16:03 GMT

hi,we have replication setup between SQL2005 to 2008, recently we are facing issue in replicaiton as " a required previleage is not held by the client"we changed the SQLserver agent service from "domain\abc1" into Local system account it worked but it is not working under the "domain\abc1"."domain\abc1" is in administrator group only.thanks in advanceRajo.

Error 208: Invalid object name ''msdb.dbo.MSdistpublishers''

D1rtyD0g — Tue, 18 Oct 2005 10:26:00 GMT

Hi Guys,

We have a server setup as a distribution server, which manages the replication to & from 3 other SQL servers.

Last night something weird happened... Replication to & from the servers are fine except for one server. You cannot edit ANY setting, remove ANY publication or subscriber, or add a publication. the following error pops up...

The Distributor is not available. Error 208: Invalid object name 'msdb.dbo.MSdistpublishers'

What's really freaky is that replication is still running 100%

Also, when you run SELECT @@SERVERNAME on the problem server, it returns NULL.

Does anybody have a clue...???

Thanks in advance!!!

The process could not bulk copy into table

er sql — Tue, 28 Dec 2004 09:55:00 GMT

Hi, I'm working with replication and I publishing some databases from server A to server B, in replication monitor from mi server A i saw a message in two publications:

The process could not bulk copy into table XXXXX.

How can I fix the error?.

Thanks a lot

Sincerely

ER_SQL

"There are already statistics on table" error 1927 - can not resolve

Brian Jones-401554 — Wed, 09 May 2007 04:41:00 GMT

I have straight forward transactional replication set up on a SQL2000 database to a SQL 2005 database. The distribution agent is on SQL2000 and is push replication.

Recently the replication has failed with the error "There are already statistics on table" error number 1927. When this occurs I have data missing from other tables aswell which is very strange.

The error is correct, and to cure it I have to remove the offending statistic on 2005 and reinitialise the replication. What is also strange is that the statistic name is not _WA but another name (and not the name of an index). Obviously this is not the ideal situation as firstly this could occur at any time and therefore leave the database unusable (and some angry users as this is a 24/7 application), and secondly a reinitialisation of the replication could take some time.

I have found an article in the MS Knowledge Base, however it does not work. The reason it does not work is because it suggests turning off the "Copy objects to destination...Non clustered indexes" option in the article. However this option is disabled and I can not change it.

Does anyone have any insight into this error, I need a direction to investigate desparately.

Thanks,

Brian Jones

Distribution Agent Error re:Could not find stored procedure 'sp_MSins_<table_name>'

Chris O'Donnell — Fri, 07 May 2010 07:52:39 GMT

We have a customer who is receiving an error on their Distribution Agent stating:[b]Could not find stored procedure 'sp_MSins_<table_name>'[/b]The problem is that the 'sp_MSins_<table_name>' Stored Procedure does exist on the subscription database.Here is some background. Our product relies on Transactional Replication, although we do not initialize the subscription database automatically. Instead we create our own replication procedures (i.e. the Insert, Update and Delete procedures) and bcp the data from the publication database and then Bulk Insert into the subscription database. This all works fine and has been replicating using transactional replication for years.A problem occurred recently because the customer attempted to re-initialise the subscription database by simply right clicking on the subscription and selecting "Reinitialize". Subsequently the replication's Distribution Agent failed with errors stating:[b]The process could not bulk copy into table...[/b]This happened for several of the tables it was attempting to initialize.This wasn't too much of a problem though. I checked the earliest transactions that were in the distribution.dbo.MSrepl_commands table and found that 2 transactions (with many commands) relating to attempts to reinitialise, such as "sync" and "SYNCSTAT". I deleted these from the distribution.dbo.MSrepl_commands table and restarted the Distribution Agent, so that the next transactions that were waiting to be replicated could be processed.The current transaction that is waiting to be replicated is now a simple insert into a table, which will use one of the sp_MSins_[tablename] procedures. It should be straight forward. The sp_MSins_[tablename] procedures all exist on the subscription database. However, we are now getting an error stating:[b]Could not find stored procedure 'sp_MSins_<table_name>'[/b]I have checked everything I can think of. The permissions are fine. The Distribution Agent is running under a Sys Admin account. The Stored Procedure exists on the subscription database. I have profiled the Distribution Agent and can see it attempting to execute the sp_MSins Stored Procedure on the correct database using the correct login, but it fails.If I copy the execution of the sp_MSins Stored Procedure from the trace and run this directly on the subscription database while logged on as the login that the Distribution Agent is using, it is successful (albeit that I put this inside a transaction that I then rollback).Any help on this would be most appreciated.

Replication/Log Shipping across a firewall

John Mitchell-245523 — Thu, 21 Jul 2005 01:57:00 GMT

Hello

We're trying to decide between transactional replication and log shipping, and I think it's going to come down to how easy it will be for the two servers to communicate. For log shipping we will need for one server to map a drive to the other, meaning the account that starts the service on one server needs permissions to a share on the other - not easy to set up if there are firewall policies to overcome and no trusted domains between the two.

As I understand it, transactional replication only needs port 1433 to be open on the firewall for the two servers to communicate (or three if we use a separate Distributor). Am I right in this?

Second, I have read that replication generates more network traffic than log shipping. Is there any way of quantifying this?

ThanksJohn