We are running snapshot replication on a non-Remedy database and it works great. Since I have an understanding of how that works and how Remedy works, I may be able to offer some suggestions: First, as you all know, the way remedy works, forms are data. That is not the case with all database application systems like ours which has an MS Access front-end so the forms are stored in Access not MSSQL. Secondly, all items in the database do not necessarily have to be replicated. It may be that your DBA didn't set this up right. I believe the main problem may be timing. Clearly if data for a changed form on the master reaches the replication instance BEFORE the change to the form gets there, there would be a problem. I don't know whether or not this should be possible with transactional replication, but it seems worth checking (and whether there is a way of prioritizing replication updates). Fluxman
_____ From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of Moore, Christopher Allen Sent: 06/06/2008 10:57 AM To: [email protected] Subject: Re: Cautionary tale? SQL Replication service and Remedy ** Phil- Thanks for the reply. I he did use transactional, which seems like it should not have caused problems, and the BMC tech we talked to said it was supported. Once he put it on the dev side, everything appeared to be fine until form changes occurred- if you have anyone looking to use it I'd definitely suggest testing it on a test/dev install and doing form changes both in the admin tool and the class manager to make sure things are acting like they should. Chris From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of Phil Murnane Sent: Friday, June 06, 2008 9:29 AM To: [email protected] Subject: Re: Cautionary tale? SQL Replication service and Remedy Chris: What kind of "replication" did your DBA set up? We have a customer looking at this type of configuration in order to create a reporting server. They're deciding between either transactional replication with a read-only consumer or a mirrored database with snapshots. BTW, we did some testing a few years ago with SQL Server 2000 and transactional replication with read-write consumers, and that failed miserably because SQL Server added columns to every table to be replicated, which of cource confused arserver.exe terribly. Thanks, --Phil __Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are" html_____Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are" html___ _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are"
