I am given with the responsibility to set up database replication in my organisation.
Before starting the replication set up, I would like to know which is the best suited replication for my application.
My application is much process oriented, and the users are working on records parallely(but with different records).
Say for ex:
There is a module for Insurance claim processing, it is handled in the following manner:
There are many employees with CSR roles, and all are working on some set of records to be processed. But No two employees should get the same record for processing. For that, we are doing locking of the cases by having one column called 'LOCKED_STATUS' and setting value as LOCKED. So that other users wont get the same case. Once the case is processed, the record is marked as unlocked.
My analysis for replication is as follows:
1. Snapshot replication: This wont be a suitable type of replication as the updations are to be immediately updated on all the subscribers, because when the user executes select query to get the next unlocked case, No 2 user should be able to get the same case.
I think, the best replication to chose from is, Transactional replication with Immediate Updation/Queued updation. But the problem is, when one of the subscriber goes offline, the updations are queued up. But in my case, say for ex. One case is updated as locked, but the subscriber is offline and the updations are queued up. At the same time, the other subscriber can fire an select query to get the next unlocked case. Since the update is on queue, there are possibilies for this subscriber to get
the same case.
Can anyone let me know, are the select statements also queued up(i.e., along with update and insert statements.)? If not please let me know how to approach for this problem.
I have one publicacion on ms sql 2005 Enterprise w.sp1/MS Windows 2003 Enterprise w.sp2 and one subscriber on MS sql 2005 Enterprise w.sp1/MS Windows 2003 w.sp2, but I have also 3 subscriber on MS SQL 2000 w.sp3/MS Windows 2000 advanced server w.sp4. They replicate the same database with a publication compatible with 80RTM, All works fine with data replication, but I can't replicate DDL to MS sql 2005 suscriber, I don't care that don't replicate DDL, but I want manually alter triggers at MS sql 2005 suscriber, but I get this error at the subscriber on when I run the ALTER TRIGGER statement :
Msg 21531, Level 16, State 1, Procedure sp_MSmerge_altertrigger, Line 67
The DDL statement cannot be performed at the Subscriber or Republisher.
Msg 21530, Level 16, State 1, Procedure sp_MSmerge_ddldispatcher, Line 181
The DDL operation failed inside merge DDL replication manipulation.
Msg 3609, Level 16, State 2, Procedure TU_Centros_Distribucion_Articulos, Line 58
The transaction ended in the trigger. The batch has been aborted.
Any help will be appreciated,
PD. I miss sql2000 replication, where I have full control over the database logic
We have three geographically dispersed offices, each with their own local SQL Server. We are creating a DB application (SQL Server 2005) for our primary business (insurance) and expect to have one database with replicas on the other servers. (There is no "primary" or home server -- each of the local replicas/servers are peers.) Users in each office will update records in the local replica of the database for clients principally served out of that office. All data, however, must appear on all replicas for business intelligence purposes. In addition, there will be some (though limited) amount of record upating in one office for clients principally served out of another office. The nature of the business is such that it is unlikely users in two different offices would be working on the same record at any one time. It is not unreasonable, however, that during the course of the day, two users in different offices might edit the same record. Therefore, data inserted/updated in one server should be replicated to the other two servers within no more than an hour or so.
Given the above, how should I approach replication? The way I read the MS documentation, I should be looking at peer-to-peer merge replication. As an alternative, I might also use a peer-to-peer topology with a transactional replication. In the latter case, however, I should be looking at updating subscribers. Some here have suggested that neither approach is necessary and that I can use plain vanilla peer-to-peer replication with straight transactional updating (or I have completely misunderstood their posts). Because there is no central server, creating "non-peer" publishers on each of the local servers doesn't seem to be an option. As a final twist, so far as I have been able to figure out, MS SQL Server Studio 2005 will not allow me to create peer-to-peer replication with anything other than straight, non-updatable, updating -- With transactional plus updating subscribers the option to enable peer-to-peer is greyed out and the menu entry to configure peer-to-peer topology does not exist. With merge replication, the option does not even exist (on the GUI) and, again, the menu entry is missing.
Any thoughts, help, comments or criticisms on this subject would be most appreciated.
I have a replicated database on 2008 R2 being moved to a new instance with 2014. Application regression testing is complete and all tests are good.
The current transactional replication topology is Publishing subscriber: the distributor is local and pushes to a subscription on an intermediary server. This server then has an identical publication and local distributor which then pushes to a subscription on a customer's server. There's no business case for this setup, it's just how it was created at the time.
I want to change this to a Central Distributor model when we do the move to speed things up and remove any extra potential points of failure.
The customer has a requirement that during this process, their subscription database remain online, all tables are fully populated and replication pick up exactly where it was left off. This is a completely new scenario for me and I was hoping to just be able to rebuild the subscription from scratch.
Is there a way to do this move and topology change and meet the customer's requirement?
I want to buy a laptop, so that I can install and play with the trial SS 2005 Enterprise Edition and hopefully get familiar with SSIS. At work I have only used SS 2000. I want a laptop which will run this with a reasonable speed, but don't want to pay for more juice than is actually required. Does anyone have any advice on what kind of spec would be good enough for SS 2005 Enterprise? If I go for the basics suggested by the system requirements, will it run like a tortoise?
I'm beginning to wonder if replication is worth the trouble I've had to spend on it!
Trying to create a simple peer-to-peer replication topology. I can create the initial publication. I can change the property to allow P2P. I can backup the database and I can create a snapshot. When, however, I try to configure the peer-to-peer topology, I get a 14027 error message telling me that ONE table out of 250, or so, "does not exist in the current database." That's pretty troubling given that I can run a select query against that specific table. I would appreciate any information that would help me to understand what's going on or successfully set up replication.
I'm new to sql and have come up with a problem and can't seem to find the answer. Most would probably find it simple but I cant get my head around it! :p I have the following table structure User_Table-----------User_ID (Key)FirstNameLastName Contacts_Table--------------User_ID (F key)Contact_User_ID User_Table stores all users details and assigns them a User_ID. Users can add other users to their contacts, and this will be stored in Contacts_Table on a one-to-many basis. *deep breath*... So User_ID in Contacts_Table, will store the User_ID from User_Table, and the Contact_User_ID in Contacts_Table will store the User_ID from User_Table. Does this seem ok? Sorry if I confused everyone! So my question is, how do I select a user and show all his contacts (names etc)? I thought I could use innerjoin but I dont think it would work here. Any ideas? Thanks!
Hi: AS a newly Master degree graduate student in IT field. My M.S. degree training has been emphasized in database developer, Web developer, Web/database developer, network, and network and computer security. My personal interesting are database and web. have experienceon java servlet and database(create a web site), try ASP and dataabase now, but I don't have any work experience(come from other country and change major)
hope can get advice from kindness prople what is suitable to learn DBA or oracle ? conside about difficult level, cost, and suite for future job market
I am trying to dump-load a db from one server to another.I don't have any problem with the dump and load , the problem is with scheduling the copying of the dump file fron server1 to server2.
I tried using xp_cmdshell 'copy filename filename ' to schedule it but it says "access denied" zero files copied...(using sa account and standard security) But when I telnet to server1 and issue copy filename filename it works fine. how can I correct this problem and schedule the dump-copy-load??????
In the near future I need to move a 27GB database from SQL2000 to SQL 2005 that is located in a different data center. I can do a backup, copy the .bak file over the WAN and do a restore, but that will take several hours over the WAN. I think the new server will be standalone, not a cluster. We have not purchased it as yet.
What options do I have to minimize downtime? I don't think I can log ship between SQL versions, but I might be able to run two instances of SQL on the new server (2000 and 2005), although I consider that an iffy proposition as well. The OS would be Win2003 sp2 on the new server. What other options do I have? Would mirroring work between versions? Thanks for any suggestions.
How do I write a query (using a union) suitable for paging I currently have a query which results from two queries combined by a union. It returns 3000 rows. I want to replace that query with one which returns only 50 rows from the relevant page [using ROW_NUMBER()]. Is there a way to do this with only 1 CTE or will I need to use two consecutive CTEs [the first get a union on the queries and the second to apply ROW_NUMBER()]. I can't see a way of doing it with only 1 CTE table. Alternatively is there a very efficient way to do it using derived tables?
I have huge table, often I need to query the table on the whole; ie., data may required at any part of the table. So I think of to compress the table with the aim of reducing I/O.
1. is that really suitable for this requirement? If So which compression is good (Row or page )?
2. Or is there any other alternate to reduce the I/O (Except Indexing)?
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!
