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,
Hi I am interested in taking MCTS exam 70-431 for sql server 2005 implementation and maintainance. I have been reading the hardware requirements for the instalation of sql server versions and realise that enterprise and developer editions have same minimum requirements for the operation system. I understand that the Developer Edition includes all the functionality of SQL Server 2005 Enterprise Edition, but it is licensed for use as a development and test system, not as a production server.
Also I undestand that the developer edition supports the Windows XP Home Edition with SP2 or later but the enterprise edition does not support this operating system. The evaluation/trial version is for the enterprise edition. Can I use the developer version of sql server 2005 for my practice exercises instead of using the trial version? I have all hardware requirements for the trial enterprise version except that I am using Microsoft windows Xp home edition version 2002 with SP2. I am trying to see if I can use the developer version of sql server 2005 as it is cheaper for me to buy this software than buying the new operating system for my computer. According to the microsoft book for the MCTS exam 70-431 there is a section which states that before you begin you should have Microsoft Windows Server 2003 running on your computer on an NTFS file system (NTFS) partition. Will I still be ok to use the book and be able to do all the tests in the book if i am using the developer version of sql server 2005 with my Microsoft windows Xp home edition than using the trial version which comes with the book?
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?
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?
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?
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?
I am using SQL Server 2000 SP4 running on a MS Server 2003 with SP2. I am preforming Merge Replication on a continouas basis and the Merge Agent keeps stopping with the error 203 The process could not enumerate changes at the 'Publisher'. There is no additional information available with this error. Does anyone have any sugestions as to why this is happening. I can manually re-start the agent but it will fail again for particular reason.
we are trying to replicate an sql server 2000 database to another sql server 2000 database.
We are having problems because at some point we deleted the column showacc from one of the tables. When we try and replicate the database we get a complaint about an invalid column showacc.
I have tried doing a select into a blank table and setting the defaults and renaming the table, but even that didn't work.
Any ideas what I can do on SQL server 2000 to get replication working properly?
We have few branches with individual dbs are sitting in the branches itself. Periodically all the data need to be updated to a single HQ database. At the moment, all the tables's primary key are unique and each branch will have branch ID's in the transaction tables.
e.g. Branch1 data need to be updated to HQ db. However, HQ db records which are related to Branch 1 data only need to be updated back to Branch 1. other branch records should not goto Branch1.
Similaryly other branch records need to be updated/replicated back to HQ database. And only records related to the particular branch need to be updated from HQ (if any changes made)..
At the moment, i can do simple replication from one db to another db only... Can anyone guide/give suggestions on how to go about doing this?? If possible, please give steps involved...
I know that SQL Server Express 2005 can subscribet to SQL Server 2000 publications. However, it seems that SQL server 2000 cannot perform a push to SQL Express.
Can anyone refer me to any online help or documentation on how a proper replication can be done between SQL 2005 Exress and SQL 2000??
I want to replicate SQL Server 2000 data from publisher to subscriber with new data added and existing data modify at subscriber, is it possible? what is the solution.
Any idea as to how SQL Server ensures that no data is lost during replication. In my project we have some across several instances where the SQL server indicates that the data has been replicated but it is not recieved at the other end. The network is not very reliable, in case the network link is lost during replication how does SQL ensure no data is lost. If you know the answers or have any documents please share the same.
I have created replication on my two servers (production and backup servers). I used wizards to create it and then generated SQL script for deleting and creating replication. For another task I came across the command sp_removedbreplication 'dbname' and I tried to use that for removing replication more easily on the servers. It seemed to not remove everything on the production server and whenever I install replication now, either by using wizards or my generated SQL scripts I get an error icon (red circle with a black X in it) on my Replication Monitor all the way down to Publisher and the publication named with the computer name. Also this icon is on Agents and Log Reader Agents but not on the actual agent.
Something must have happened when using sp_removedbreplication 'dbname' and I can't fix it. The replication works properly but i wish to not have the error icons.
Does anyone know how the error icons can be removed?
Hi, I posted about this before, and set out on my own to get this working, and haven't been able to. I'm trying to get merge replication working with my SQL server 2000, and after 2 weeks I still have nothing. I've gone through multiple 'walkthroughs' which all brought me to the same point. I'm getting down to crunch time, and I'm either going to use this or implement my own merge algorigthm (I'd much rather use this). So here's where I've gotten to:
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.
Hi, I am trying to replicate a production database server,on sql server 2000 at a particular geographic location to a new failover database server on sql server 2000 in a different geographic location via internet. The intention here is to use the failover database during times when the production server is down or busy and the synchronization needs to be sceduled for every 10 min. It will be of huge help if any expert could give the detailed process involved and any precautions that need to be taken. I also need to keep inmind to use the ever/odd sequence number generator during the replication implementation. Also, Whether to use row-level or column-level tracking?
I'm new to this forum, though not new to sql server am new to DB2.
We are running Microsoft SQL Server 2000 but we have recently acquired similar business in another country which runs IBM DB2 database system. We are interested in incorporating the data from DB2 in our system. The tables are slightly different in DB2. Q. what is the best way to integrate the two systems? Should we take the route of a federated system or replication of data? We are interested in knowing what is happening in the other business (DB2) but we what the two systems to operate in parallel for about a year, before we come up with the best solution.
The company is after a short term and long term solution.
Can any one please help or point me to the right place?
Hi. I'm creating a new publication for replication. There are a few columns on our main database I do not want published as they contain some confidential information. When I go to create a new publication, I go through the wizard and I select the option to filter rows vertically. I uncheck the columns I don't want published and the wizard completes without any errors.
When I go to start the Snapshot agent to create the database on new server, it gets error saying it cannot find certain columns--the columns I do not want published to begin with.
Am i doing something wrong? I appreciate any help you may provide!
I do a merge replication between Sql server 2000 and SQLCE 2.0
On my SQL2000 I have 4 tables i want to merge (specific columns only ) in 1 table for Merge with my SQLCe ( the table will be use for read only)
Question 1: What is the best pratice for keep the information update? Run store procedure before the synch for re-populate the table?:confused: or Make Trigger INSERT, UPDATE, DELETE in the all 4 table?:confused: or a mixte?:confused:
Question 2: Does someone know about some web site talk about this type of trick?
All my queries are being blocked while the tables are being replicatedand it is causing some 2 minute blocking. Is there a way for theReplication to allow dirty reads because I really don't care aboutthat, I would rather have dirty reads than 2 minute waits.Thanks.
Hi,I'm in need of detailed information on how data replication works on thesql server 2000. If someone knows about a book or articles thatdescribes how data replication works with transactions, storedprocedures and/or merging databases I would like to be pointed in theright direction./Zero_Addiction.
I am carrying through a replication of the transacional and heterogeneous type between the SQL Server 2000 and MySQL 5.0.41, through driver of ODBC of the MySQL (version 3.51.15).
Unhappyly I am not having success!
I make all the necessary configurations, but in the hour to create schema in the MySQL, only the table msrepl7 is created (but nondata) and occurs the following error: €śDate too long will be column €śtimecol€? at row 1€? and later €śInvalid cursor state€?.
The first error must to the size of the column timecol that it is created as char (16), but the value that goes to be inserted is to char (19) - > ({ts'2007-05-01 20:45: 21 '}) The table that is published has only two entire fields and the same one is not created in the MySQL, exactly with the option to initiate schema. I looked for in some sites and I found one that said to bind query Log of the MySQL and to catch the command of insert for the table msrelp7 and to insert in the hand, after making this to come back to the SQL Server and to ask for to synchronize again. Did not function, now only with the error of €śInvalid cursor state€?! To complete one another person in one another site it placed that was to exclude the table msrepl7 that everything would function, did not function!
