SQL 2008 SP1 - Replication DB

Hi, I am attempting to get merge replication going between two SQL 2008 servers.  So far, everything has gone off without a hitch with one exception.  We use spatial data on a daily basis in my organization, so we implemented the geography data type.  This data type seems to be causing all of our replication issues.  I can easily create publications and subscriptions for each article in the entire database except the geography field. The error is as follows: "The Merge Agent failed because the schema of the article at the Publisher does not match the schema of the article at the Subscriber. This can occur when there are pending DDL changes waiting to be applied at the Subscriber. Restart the Merge Agent to apply the DDL changes and synchronize the subscription." The real kicker is that the schemas are exactly the same.  If I set the publication to drop and recreate the subscription article, then to convert the geography data type, it works without issue, but then we run into issues with our publication database not matching exactly with our subscription database, which could cause many potential problems with our web front end.   Is there a known issue with replicating the geography data type?  Any help is very much appreciated! - Chad  

Dears, I am make a testing environment before implementing it into real world. I have 3 servers SQL 2008 R2, i configured 1 Publisher, 2 Subcribers with a merged replication. Everything is Ok. However, i have an ID field on Publisher which is autonumber(Start by 1, increment by 1). When I try to add new record on publisher, it takes it 1 by 1 i.e. 1-2-3.... But i try to add it on subscriber it starts with 20,000 i.e. 20001, 20002. I think this is logical for SQL, but can i define this number on the subscriber? So it will start on 200,000 for example? Another question, In LAN i can connect the subscriber to the publisher, it will connect to it directly, since it is broadcast. But in WAN environment how can the subscriber detects the publisher??? Your reply is highly appreciated, Thanks in advance,

we upgraded to Sql 2008 standard edition last night from 2000 and our replication is now failing, cannot delete it or enter new ones.   I found one article saying the following stored procedures need to be run to upgrade the replcation:   exec sp_vupgrade_replication  exec sp_vupgrade_repl_metadata   however the first one throws and error and the second one seems not to exists.  does anyone have any insight into this. or how to delete the replications?   the error from the stored proc sp_vupgrade_replication  is :   Upgrading subscription settings and system objects in database [SoxAuditSystem]. Attempting to copy article resolvers from SOFTWARE\Microsoft\Microsoft SQL Server\MSSQL10.MSSQLSERVER\Replication\ArticleResolver Msg 25026, Level 16, State 1, Procedure sp_registercustomresolver, Line 82 The proc sp_registercustomresolver cannot proceed because it is not run in the context of the distribution database, or the distribution database is not properly upgraded.  

Hi,    We were using SQL Server Transactional Replication between two SQL Server 2005 servers. Now we are going to upgrade the Publisher server to SQL Server 2008, Distributor Server remains as SQL Server 2005.     Can anyone let me know what is the challenges we need to face when configuring Replication between SQL Server 2005 and SQL Server 2008. Replication Method - Transactional Replication Distributor/Subscriber - SQL Server 2005 Publisher     -  SQL Server 208 Regards, Fazlu.

How do I clear transactions from log due to a failed attempt to setup replication?

I have an ASP.NET application that uses replication, and uses the RMO DLLs to do this. I initially built the application against the 2005 version of the DLLs and have it running successfully against SQL Server 2005. However, when I try running it against SQL Server 2008 it doesn't work. Initially I didn't deploy the Microsoft.SqlServer.* DLLs with my app - instead relying on them being in place on the server on which it was installed. However, when trying to make it work against SQL Server 2008 it was looking for the 2005 version DLLs which it wasn't able to locate. Following some other advice I read online I have now swapped out the 2005 DLLs and referenced the 2008 assemblies in my .NET project. In my MSI I now also deploy (i.e. redistribute) the SQL Server 2008 DLLs to the bin folder of my ASP.NET project. Now, when I try to run the application against SQL Server 2005 it fails to load the Microsoft.SqlServer.Replication assembly. I run depends.exe against this and find that it's dependent on SQLNCLI10.DLL which is missing on my machine with only SQL Server 2005 on it. So, what am I to do? Is this possible? How do I get around this?

Hi, I am trying to replicate data from a sqlserver to an oracle 11 subscriber(push subscription). I recently moved to SQL server 2008 from 2005. The replication in 2005 worked ok, and now in 2008 - it does not. The problem: It tries to make some fields as an interval data type in Oracle. For example, nvarchar(3) are turned into interval and numeric(38,8) fields are turned into nvarchar2(40). Anyone has any idea why is this happening and how can I change it?

I need to give a user access to Replication Monitor in SQL 2008. How can I do this without giving them SA access ?  

In 2000 sql error occurred when the replications showed the line and record with, exactly what record. As I see it in sql 2008?

Hi all, I have setup transactional replication on my PC with SQL 2008 R2, and successfully added some row filters on certain tables. This has worked great. However, our production server is on SQL 2008 (not R2) and as such I thought I best try it works the same on the older version.  Unfortunately the row filtering seems to have had no effect. Can anyone confirm if there was a problem in the previous version so I know if the production server must be upgraded or if I just have something badly setup. Thanks for your help. John

Dear All, Im new in SQL, would like to what will be the consideration and effort from [WIndows Server 2008 STd with SQL Server 2008 STd] and replicate over to another location with same setup? Is there any guide which could describe the steps for this?  

Hi, I am not an SQL expert, but have to set up 3 remote SQL databases that need to be synchronised with each other. This is unusual because the locations are tiny atolls in the middle of the Pacific.  Communication between them is by satellite only which has limited bandwidth and is expensive.  The total population (thats all the people) on each atoll is only 500.  There is likely to be a maximum of 40 potential users per atoll and each SQL database is for internet login authentication only (Radius).  So the databases are tiny and have a very low update rate. What is the simplest way to synchronise the databases?  Doing this just once each night at around 4:00am would be best.  Peer to peer replication sounded right, but I do not want our extremely limited bandwidth taken up by this traffic when all we need is for the databases to be synchronised by the next day.  Also we are running MS SQL 2008 R2 Workshop edition and I am reading that this does not support peer2peer replication. The hardware is a laptop - since hot moisture laden salty air is very corrosive for traditional servers and power is intermittant at best.  Each atoll gets an identical system. Can anyone suggest a solution or ideas?  I am happy yo answer questions.  Thank you.

Hi, i want implement sql 2008 merge replication (view this for info: http://social.msdn.microsoft.com/Forums/en-US/sqlreplication/thread/378a993a-3c96-454b-9250-b0b600725659) . Now, i don't find info for install 2008 merge replication step-by-step. Can you help me? Thanks to all in advanced.Mino

First, can SQL Server 2008 R2 replicate to SQL Server 2008 R2 Express Edition???

Second, I have setup replication from R2 to a SQL Server 2000 database.  I defined a stand-alone table (not a parent or child) and replication worked fine.  I simply changed a record and it was reflected in the 2000 database.

Next, I changed the table to be replicated to be a parent table.  After I changed a record in this table, replication failed.  The error message said it was unable to drop a table because it was in a relationship.

Questions.  When replication occurs between a publisher and subscriber and several records in a table targeted for replication, is the table dropped in the subscriber database then copied over in its entirety???  When I define a table to be replicated, do I have to include all the related tables???

 

Thanks.

Hello All !

I have some questions about replication with SQL Server 2008 --> context

An offshore team has developped a Web application (IIS 7/.Net 3.5). The databases are stored on volumes hosted on a SAN (Windows 2008 cluster 2 nodes with SQL 2008 SP1 in A/P mode)

Special queries and results (insert/update/delete) are stored in database on cluster

Special consultation queries (select only) are redirected to another server which will contain the database copy) in order to create realtime reports

Log shipping and mirroring can't be choosed because this application needs real time.

I want to know if it is possible to create a solution with cluster and replication. If yes, waht is the prerequisites and how to do that ?

---

Thanks for advance for your ideas / help - Regards - Have a nice day ! RHUM2

I have a publication on SQL Server 2008 Standard Edition using merge replication.  When I attempt to generate the initial snapshot, the snapshot agent appears to hang on the step "Setting up the publication for filtered articles."  I get a long (over 4 hour) series of messages: "The process is running and is waiting for a response from the server."  I know something is happening server-side, as SQL Server and the snapshot agent use a lot of memory and max out one core's processing capacity.

This has me confused as the publication is not doing any filtering.

Even more confusing:  I backed up the database and restored it onto my development-test system.  I created the snapshot there, and it took under 10 minutes every time.

Any suggestions for investigating and resolving this?

Currently running merge replication on SQL Server 2008 10.0.1600 and having issues with adding and modifying triggers on published articles.  I've searched through the MSDN site and googled it but have not found any definitive information on correct procecdures.

We have a replicated table that had 1 trigger on it when it was added to the publication.  That trigger was replicated.  We have since added a 2nd trigger to the table and it is not being replicated to our other server.  I've checked the Article Properties and Copy User Triggers is set to TRUE.  The only difference is the new trigger has NOT FOR REPLICATION in it, but I thought that would only keep it from being executed if a row is effected by the MERGE process.

We have rerun the snapshot and are syncing continuosly and the trigger does not replicate.  Do I have to drop the tablefrom the publication and then re-add it?  Am I missing something? 

Thanks.