I have Replication working on 2 servers running SQL Server 7.0 with SP3. I am replicating select tables from 3 databases using Transactional Replication. I setup P1 as the publisher and the home for the distribution database and P2 is the Subscriber. I setup a push subscription to P2. It is working fine. Just one issue. On P2, I don't have Replication Monitor and I'm not sure why. We just installed SP3 on these two servers. In order to do this on a Clustered environment, we were forced to drop replication and then re-add it after installed the SP. After all this was done, I re-added replication and now P2 does not display Replication Monitor.
DBCC OPENTRAN shows "REPLICATION" on a server that is not configured for replication. The transaction log is almost as large as the database (40GB) with a Simple recovery model. I would like to find out how the log can be truncated in such a situation.
I have a setup where I need to replicate the database which is actually subscribing from another database. The current setup is all in SQL Server 2000. I need to now setup a Distrbutor on a SQL server 2005 and publish the database using this distributor to another server on SQL server 2000.
Has anybody done this before. If yes what will I need to check. Can you please let me know :-
1) SQL Server 2000 which SP should be installed to support this enviroment.
2) SQL Server 2005 which SP should be installed to support this environment.
We have a SQL Server 2000 ent edition sp4 with 3 small databases and one 4 GB database which is REPLICATED The Server has been bouncing like a yoyo today because of a disk controller problem and I am preparing to move the Instance to a whole new server this afternoon. The new Server will have the same IP and name as the original server.
Any suggestions for the easiest or most seamless way to make this happen? preferably using Backup and Restore since they plan on taking the old server down completely and then building a new server with the same name and IP ... any suggestions would be appreciated.
SQL Server replication requires the actual server name to make a connection to the server. Connections through a server alias, IP address, or any other alternate name are not supported. Specify the actual server name, 'xxxxxx'. (Replication.Utilities)
Transactional replication allows updatable subscriptions where changes at the subscriber are replicated up to the publisher, this can happen via Immediate Updating subscriptions, Queue subscriptions and P2P (new in SQL 2005), all forms of Transactional replication.
Any compared document between merge replication and Transactional with updatable subscribtion ?
I'm looking at a setup where they have server1 and server2 in a mirroring relationship with automatic failover.
Server1 is the principalThey are using transactional replication to replicate asingle databse to server3 is AWS.Distribution database is on Server1All Agents (log reader, snapshot, distributor) run on Server1Server2 has not been set up for replication...My understanding is that in this set up you would normallly place the distribution database on a separate server and enable publication on the mirror, Server2.
What happens if they failover? Replication would stop, and presumably records added while the mirror is the active database would not be marked for replication?How would they recover? Failback and reinintialize
I am trying to test simple replication (only tables) of a database that resides on a SQL Server 2005 instance to a SQL Server 2000 instance. The Publisher and Distributer are set up on the SQL Server 2005 instance for Transactional replication. The subscriber is set up on in the 2000 instance. Replication Monitor shows the following error after applying a few scripts: "Category: SQLSERVER Source SQLSERVER2000 Number: 170 Message: Line 6: Incorrect syntax near 'max'."
Here SQLSERVER2000 is the name of my 2000 instance, as should be obvious.
Beyond this point, replication fails. Any pointers as to where the problem could lie? Is this a known backward compatibility issue? I've checked all tables in the database and none contain any datatype that is new to 2005 (the database was actually created in and for SQL Server 2000.
Replication from 2000 to 2005 works fine, but the other way round is failing as described above. Any clues?
Let say I've 4 server with MS SQL 2000 installed and I want all of them having the same data. So I'm using merge replication by assign one of them as publisher/distributor. The problem is when ( let say ) server that have been assign as publisher/distributor down then all the other server cannot make replication. My idea was to make it replicate to other available server ( among them ) if replication to main server failed. Is it possible ? If possible how to do it ?
I am working on my graduation project that has a wide section of PC Pocket application to merge data between the SQL Mobile Edition and the SQL Server 2005. So, i had done most of the steps mentioned in the Books Online for the SQL Mobile Edition, till i had reached the step of creating a subscription for the Mobile Database, it is known that at the end of this step there would be a code generated in order to use it in developing the application and after clicking finish the wizard will start Synchronization. Here this step fails with a message informing me that the snapshot agent is not started yet or the publisher didnt generate the snapshot yet !!
I'm getting this, after upgrading from 2000 to 2005.Replication-Replication Distribution Subsystem: agent (null) failed.The subscription to publication '(null)' has expired or does notexist.The only suggestions I've seen are to dump all subscriptions. Sincewe have several dozen publications to several servers, is there adecent way to script it all out, if that's the only suggestion?Thanks in advance.
Hi,I have transactional replication set up on on of our MS SQL 2000 (SP4)Std Edition database serverBecause of an unfortunate scenario, I had to restore one of thepublication databases. I scripted the replication module and droppedthe publication first. Then did a full restore.When I try to set up the replication thru the script, it created thepublication with the following error messageServer: Msg 2714, Level 16, State 5, Procedure SYNC_FCR ToGPRPTS_GL00100, Line 1There is already an object named 'SYNC_FCR To GPRPTS_GL00100' in thedatabase.It seems the previous replication has set up these system viewsSYNC_FCR To GPRPTS_GL00100. And I have tried dropping the replicationmodule again to see if it drops the views but it didn't.The replication fails with some wired error & complains about thisviews when I try to run the synch..I even tried running the sp_removedbreplication to drop thereplication module, but the views do not seem to disappear.My question is how do I remove these system views or how do I make thereplication work without using these views or create new views.. Whyis this creating those system views in the first place?I would appreciate if anyone can help me fix this issue. Please feelfree to let me know if any additional information or scripts needed.Thanks in advance..Regards,Aravin Rajendra.
In my production box is running on SQL7.0 with Merge replication and i want add one more table and i want add one more column existing replication table. Any body guide me how to add .This is very urgent Regards Don
Hello,I'm getting the following error message when I try add a row using aStored Procedure."The identity range managed by replication is full and must be updatedby a replication agent".I read up on the subject and have tried the following solutionsaccording to MSDN without any luck.(http://support.Microsoft.com/kb/304706 )sp_adjustpublisheridentityrange (http://msdn2.microsoft.com/en-us/library/aa239401(SQL.80).aspx ) has no effectFor Testing:I've reloaded everything from scratch, created the pulications from byrunning the sql scripts generated,created replication snapshots andstarted the agents.I've checked the current Identity values in the Agent Table:DBCC CHECKIDENT ('Agent', NORESEED)Checking identity information: current identity value '18606', currentcolumn value '18606'.I check the Table to make sure there will be no conflicts with theprimary key:SELECT AgentID FROM Agent ORDER BY AgentID DESC18603 is the largest AgentID in the table.Using the Table Article Properties in the Publications PropertiesDialog, I can see values of:Range Size at Publisher: 100,000Range Size at Subscribers: 100New range @ percentage: 80In my mind this means that the Publisher will assign a new range whenthe Current Indentity value goes over 80,000?The Identity range for this table cannot be exhausted! I'm not surewhat to try next.Please! any insight will be of great help!Regards,Bm
I am trying to replicate data from SQL Server 2000 to SQL Server 2005.previously we did it from 2000 to 2000 using script.
but when i am tring to use that script with 2000 to 2005 its not working i have made the necessary changes in the script.Is there major changes to replicate from 2000 to 2005
I have a VB.net app that access a SQL Express database. I have transactional repliaction set up on a SQL 2000 database (the publisher) and a pull subscription from the VB.net app. I use RMO in the VB app to connect to the publisher. My problem is I am getting some strange behaviour as follows
- if I run the app and invoke the pull subscription it works fine. If I then close my app and go back in, I can access my data without any problem
- If I run the app and try to access data in my SQL Express database it works fine. I can then close the app, reopen it and run the pull subscription it works fine
however.......
- if I run the app, invoke the pull subscription (which runs fine), and then try to access data in my local SQL Express database without firstly closing and reopening the app, I get a login error
- if I run the app, try to access data in my local SQL Express database (which works fine), and then try to run the pull subscription I get a "the process cannot acces the file as it is being used by another process" error. In this case I need to restart the SQL Express service to be able to run replication again.
I get exactly the same behaviour when I use the Windows Sync tool (with my app open at the same time) instead of my RMO code to replicate the data.
I am using standard ADO.Net 2 code to access my SQL Express data in the app and closing all connections etc
I want to test SQL Server replication. Can I create two databases and replicate between on the same server as to give me an idea on how replication will work?Or should I use two completely seperate SQL servers to test replication?Any good links to setting up the replication?Thanks!
I am following the wizard to setup SQL Replication. My understanding is that I can create the Publisher and Subscriber on the same SQL database server. I have setup two databases TestA and TestB and TestC being the publication database, on the same server DatabaseA. The first warning I receive is that SQL Server Agent on Database A currently uses the system account which causes replication between the servers to fail. In the following dialog box, specify another account. I have set up another user account for DatabaseA with full writes to everything and specified the user account in the dialog the warning message spawned. I have put the SQL Agent user in all three database I followed the rest of the wizard and on the Specify Articles to Publish, Tables appear as the object type, Show is checked and Publish Article is unchecked. I try to check Publish Article for the tables object, and it is locked and I cannot go any farther in the wizard.What am I doing wrong? Do I have to use two different servers to do replication?Please advise!Thanks!DotNetNow
Hi, Has anyone done replication from SQL Server 70/NT to DB2 before? Anyone has any tips or guidelines which may help me in going for it - like rights/permissions/certain Stored procedures/certain service packs etc... Any help appreciated. pvd
Our MS SQL Server Tables(2 Nos) needs to updated in the AS/400 Server every day. How do i proceed with? Is there any tool is avaliable? or MS SQL Server / Windows NT will have the provision to communicate and update in AS/400 Server.
Dear Listers, I need to replicate a certain table from the SQL Server Data Base on NT to the AS/400 (as subscriber). It is only one way, and I know that some product by starsql will probably work. I do not know the details and am a little foggy about them. Can someone point me to an source of information on the sharing of data between NT and AS/400?
We are trying to setup transactional replication across the Internet where the publisher and the subscriber are on different domains. Is this possible?
We want to implement bi-directional replication with sql server 6.5.
Do you know companies that have software products that can implement bidirectional replication for sql server 6.5? We have one central server and 5 region servers.
I believe someone in this forum replicate using tcp/ip. I am trying to do one for the past one week, facing an error message " not able to establish a trusted connection". I read the books online, Microsoft tech help,none give me a solution to this.. Can someone help me out.
I hope someone can shed some light on a problem I'm having with SQL replication. I need to setup replication to a server on the other side of a firewall. Both boxes are SQL 6.5 and are using Standard security and multi-protocol. The publisher/distributor is a member of a domain and the subscriber belongs to a workgroup. Problem: How can I replicate between these servers without opening every port above 1024 for RPC as Microsoft suggested?
I have been trying to use SQL Server replication for synchronizing offline slices of data with our main corporate database. I have been playing with replication for the last couple of weeks, but have a few problems. I have a merge publication in the corp database and have pull subscriptions in each of the slices. I use the SQLMerge object. One slice always works but when I tried another slice on another box, it kept complaining "subscription is invalid" and "call {sp_MSgetreplicainfo(?,?,?,?,?,?)}" error. it seems like the values for the subsriber, subscription_db etc are not being passed to this stored procedure. If you have any suggestions or good references on Replication, could you please let me know. Thanks,
Hi everybody I would like to ask a question, maybe stupid. I've got a sql server database and i would like to implement replication. First of all i would like to know if there's any special requirements that my database must meet before implementing replication. All of my tables got a column named "ID" wich is an int 4, identity. Can i implement replication without making any changes to my database ?
I am planning on setting up disaster recovery configuration. It is planned to use transactional replication from the production server to the DR server. Are there any recommendations for replicating changes back to the production server, once it is back online. I suppose that it would be safest to move the database back the other server over a weekend or during downtime. But I am just wondering whether anyone has experience of other practical solutions.
Is it possible to increase the replication size of tables from 250 columns. I currently have 3 tables of the DB that are 350 plus columns. (No ididn't design this DB, I know the meaning of a relational DB). Replication stops at 250 columns so I can't repliciate to different instances of SQL.
Could any body advise me of a work around on this? A third party software would ba acceptable.
