I am trying to set up transactional replication (not immediate updating) via a push subscription between a SQL 7.0 Server and a SQL 2000 Server. The SQL 7 server is the Publisher / Distributor, and the SQL 2000 server is the subscriber. Replication will not work between the two, I have removed then setup replication to no avail. The SQL 7 server always reports that it can't connect to the SQL 2000 server. Same problems the other way if I try a pull subscription.
Hi, I have no idea of SQL2000.Can anyonetell me steps /precuations involved in going for Replication in SQL2K. Also,How do we do log shipping in SQL2K? TIA pd
I'm trying to replicate a sql 7.0 table to a sql 2000 server. Does anyone know how I can register a sql 2000 box through Ent. Manager onto 7.0? I've been told that I need to upgrade my production server's Ent. Manager to 2000 but I not sure if that is a real safe bet. Can anyone give me any insight to this?
I am trying replication on sql 2000 I want to do replication using two databases. suppose say Db1 and Db2 if new record is added in db1.table1 then the same record should get added to Db2.table1 and vice versa.
using enterprise manager I have successfully created replication from Db1 to Db2.
how to do it from Db2 to Db1? any suggestion would be helpful. thanks
How do I know whether the record in a row was insert,update and delete that replicated to a subscriber? Is there a flag or an indicator in msmerge_contents,msmerge_tombstone ,msmerge_genhistory tables or any other msdb/replication system tables?
I would like some simple input on achieving true two-way replication with SQL 2000. We have need to load balance our website between two sites and since it is SQL based, would need to have dual DB servers at each site with two-way replicated data. They would need to be replicated at real-time. Will the built in SQL replication tools work OK? Has anyone done this? Thanks in advance.
Here is what we are trying to solve:-We have a SQL 6.5 server (version 6.50.258) we will call SQL65-A, onan NT 4.0 machine (version 4.00.1381), on Domain-A-We are trying to replicate directly to a SQL 2000 server (version8.00.818) we will call SQL2000-A, on a Windows 2000 machine (version5.00.2195), on Domain-B-We also have a SQL 6.5 server we will call SQL65-B in Domain-B-The domains are trusted-We get the error that it cannot connect to the SQL 2000 server whentrying to replicate, even though I can register the SQL 2000 server asa Remote ServerThe work-around we have right now is replicating from SQL65-A toSQL65-B, then using SQL65-B as a subscriber as well as adistributor/publisher to SQL2000-A.
I doing a transactional replication with two servers. Server A, the Publisher and Distributor. Server B, the Subcriber. I did the replication using a dummy DB for practice purpose and it works fine. When I try to implement the replication in original DB, I found that some tables don't have primary keys and to be able to implement transactinal replication all the replicated tables need to have a primary key. I want to add the primary keys to those tables and also implement the replication but the problem is those tables have data in it. I'm thinking in create the new table and do a DTS to import the data to the new table or it's fine just to modify the table in design to add the primary key "Those table have record in it".
I am using MSDE 2000 for replication of my Data. I have one publisher and two subscribers. but i need t filter rows for publications. Problem is that for filtering, i need host_name and in push replication host_name is name of system in which Agents are running but in MSDE all agents are running in publisher system ( distributor System). so everytime for any publication i get only id of server. i am facing same problem in pull replication also.
Any suggestions on how to replicate from AS/400 to SQL Server 2000?
Data is stored on a AS/400, but applications use a SQL Server 2000 DB. Currently, DTS packages drop the SQL DB, rebuild the tables from a script, copy the data, and then rebuild the indexes as a nightly batch job. Is there a better way to do this? Also is there a clean way to replicate daily transactions as well?
This may be in the wrong forum, but I have a database in SQL Server SP3a that I will be replicating out to SQL Mobile 5.0. The setup of the replication will not be a problem, however, once replication is setup, I will have to change the DTS Package that creates these tables.
I have created a DTS Package that drops the tables and recreates them from a DB2 database. My problem is that I won't be able to drop these tables once a publication has been established.
I really don't need to drop the tables if I can create a script to pull just the new records from the DB2 database.
Does anyone know of an easy way to do this? Are there any products out there that would make this easier? Has anyone else out there had to create a publication with this scenario?
Just a little background, I originally created the DTS Package from an import, and then modified it. I added the DROP TABLE scripts so that I wouldn't just append the same data over and over. Perhaps there is a better way of doing this than a DTS Package.
This would probably be a lot easier to handle if I weren't pulling from a DB2 database because I would probably be able to create a trigger or something on the source database, however I know nothing about DB2 datasets other than how to pull the data out. I would appreciate any input on this.
I'm trying to determine if it is possible to do many to many replication in sql server 2000.
What i basically want is to have n databases share the same basedate (share a common database) and allow updates in any database to be replicated to all the other databases (with a simple conflict resolution, like last update wins).
My goal is total autonomy, without a single point of failure. If any node goes down, the other nodes will continue to work and continue to replicate their data to the remaining nodes. When a node comes back up it will catch up with the over nodes (or get reinitialized if it was a serious crash).
The amount of data i want to replicate is not that big (less than 100MB) and does not change that often. All servers are sql server 2000 instances connected by a gigabit network and the number of nodes involved is less than 10. Some latency is also acceptable.
the question is: is this at all possible? I have read i bit in 'SQL Server High Availability By Paul Bertucci' and some other resources and it looks like a multiple publishers or multiple subscribers with merge replication setup should work, but i'm not too sure if it will work for n > 2 nodes (where all nodes publish and subscribe to each other) and it also mentions constraints on which data a given node is allowed to update (i hope this could be handled by simple conflict resolution).
And if it is not possible in 2000, could it be accomplished en 2005?
Morning Guys, If one was preparing to Replicate a database and need to know how much more size would be needed to accomadate the distribution database and its transaction logs etc... what performance counters would you set to gather this information and or tools...?
How to go about finding the average tranaction size.... number of transactions per day.... via profiler.... perfmon.... any suggestions or good sites for replication would be greatly appreciated... thanks,
Hello I am facing a very severe problem in SQL Server 2000 replication and here's the description : I had setup a replication having Publisher and distribution on the same server. Later I found out that the Subscriber database was incorrect and so I dropped the replication and then disabled it so as to start from fresh. Now as soon as I start to configure the Publisher/Distributor I get the following error message : "Error 18483 Could not Connect to ABC Server because distributor_admin is not defined as a remote login at the Server " Please let me know what can be done to resolve this issue
Please help me to resolve this issue as we need to have the replication latest by Sunday 4/21/2002
I'm trying to configure replication between a Sybase ASE Database Server and SQL Server 2000. Sybase ASE Database will be the Publisher and SQL Server will be the Subscriber. Can anyone advise me on how I can go about setting up the replication for this?
In my present environment I have two SQL 6.5 servers, one defined as Pub/Distrib the other as a Sub. I am performing transactional replication at 5 minute intervals. I have recently setup a new SQL 2000 Server and want to establish it as a subscriber to the 6.5 server (it will eventually get upgraded but I am not in control of this). We I try to add the new server to the present Distribution server I get an invalid server name message.
The server name is "NA-ALL-PR-DS01". It seems to be working fine from an NT and network / SQL server level. Any ideas would be appreciated.
I've got a nagging problem with the snapshot agent not being able to connect to the distributor.... I have a set up as follows.
I've set up the machine as a publisher, and as it's own distributor. Both the SQL Server and SQL Server Agent services are configured to run as the Administrator user (not ideal I know), and I've created a publication ready for replication. (the agent and distributor are on the same machine)
When I try and run the snapshot agent, Enterprise Manager just times out but a log in the event log says:
Event ID: 203 step 2 - The process could not connect to Distributor 'X'.
Thats about all the info I can find, nothing else is being logged.
Can anyone suggest anything I might have missed? - it's driving me up the wall!
Ok here is the deal...We have our current dev box running SQL 2000 SP3We have two new desktop boxes that we are using as a test, they are both running SQL 2005 SP1The Dev Box = PUBLISHERDesktop #1 = DISTRIBUTORDesktop #2 = SUBSCRIBERAll three SQL Servers are using the same Domain Account to run SQL Agent and SQL Server processes.When I try to create a publication from the publisher, while running the sp_addpublication step through the UI (or thru SQL Query Analyzer) I get the following error message:Msg 15404, Level 16, State 10, Procedure sp_grant_publication_access, Line 136Could not obtain information about Windows NT group/user 'crumpte', error code 0xffff0002.So as a test I tried using our subscriber box as the publisher and had it point to the same distributor box to act as a distributor - and the publication was created fine.It seems to be an issue using SQL 2k as the Publisher and SQL 2005 as the distributor. From the research that I have done, I found this KB article:http://support.microsoft.com/default.aspx?kbid=830596Which essentially says to install the latest SP for SQL 2k, which would be SP4, in the past I know there were issues with AWE memory allocation.Q1. Has SP4 been hotfixed to resolve this AWE issue?Q2. Has anyone here successfully setup replication from SQL 2k -> SQL 2005 using SQL 2005 as the distributor?Thanks!
I have set up transactional replication on two servers. The productionserver (PSERV) and a backup server (BSERV).
On PSERV I have started the agents Snapshot (running with status Succeeded) and Log Reader.(running with status Idle and the message "No replicated transactions are available").
On BSERV I choose start syncronization on my subscription. When I go into Job history I can find the following information on four lines: The job failed. The Job was invoked by User SERVAdministrator. The last step to run was step 1 (Run agent.). The subscription to publication '(null)' has expired and does not exist. The step failed. Connecting to Distributor 'SERVP' Connecting to Subscriber 'SERVB'
Anyone that have any ideas on how I can fix this problem?
