I'm guessing we will be better off with SQL Server 2005 database
mirroring - I don't think it adds any key columns, but then I have not
looked. We had at least one dev/test 7.x ITSM 7 environment mirroring
for several months last year, but I don't have it reinstated on
production yet.  The intent was to have a failover AR server ready to
load up the mirrored database, but the AR server would not be running
concurrently with production.  Has anyone else tried this, successfully
or not??

 

Christopher Strauss, Ph.D.

Call Tracking Administration Manager

University of North Texas Computing & IT Center

http://itsm.unt.edu/ <http://itsm.unt.edu/> 

 

From: Action Request System discussion list(ARSList)
[mailto:[EMAIL PROTECTED] On Behalf Of Nall, Roger
Sent: Friday, June 06, 2008 2:03 PM
To: arslist@ARSLIST.ORG
Subject: Re: Cautionary tale? SQL Replication service and Remedy

 

** 

Chris,

 

We have been using transactional replication with SQL for about 4 years
now. It works like a charm. Of course we are still on SQL 2000. There
are some challenges. 

 

>From a SQL standpoint Remedy really does not declare a primary key on
the tables. We all know that it is C1 but according to my DBA it is
really not declared so that is the first hurdle. The second hurdle is
any table marked for replication cannot be altered until the replication
process has been dropped. So when you want to change a form you must
drop replication and re-initialize. By the way, the re-initialization
process can leave your ARSystem database unavailable until it is
complete.

 

When you add fields(columns) to your forms unless you include the new
filed in the publication  they will not automatically be in the
replicated table.

 

HTH,

 

Roger A. Nall 
Manager, OSSNMS Remedy 
T-Mobile, USA 
Desk: 813-348-2556 
Cell: 973-652-6723 
FAX: 813-348-2565 
sf49fanv AIM IM 
RogerNall Yahoo IM 

  _____  

From: Action Request System discussion list(ARSList)
[mailto:[EMAIL PROTECTED] On Behalf Of Moore, Christopher Allen
Sent: Friday, June 06, 2008 10:57 AM
To: arslist@ARSLIST.ORG
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: arslist@ARSLIST.ORG
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___ __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"

Reply via email to