/Looong-update-times-on-ARSCHEMA-tp26202209p31806727.html
Sent from the ARS (Action Request System) mailing list archive at Nabble.com.
___
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
attend wwrug11
,
Alkan Koray
--
View this message in context:
http://old.nabble.com/Looong-update-times-on-ARSCHEMA-tp26202209p31800734.html
Sent from the ARS (Action Request System) mailing list archive at Nabble.com
, June 08, 2011 9:40 AM
To: arslist@ARSLIST.ORG
Subject: Re: Looong update times on ARSCHEMA
Hello Derek,
I have been facing with the exact same situation as you are since for a
while sparodically. Although I have been in contact with BMC for months -
believe me - I still have no progress
@ARSLIST.ORG] on
behalf of Rick Cook [remedyr...@gmail.com]
Sent: Wednesday, June 08, 2011 11:49 AM
To: arslist@ARSLIST.ORG
Subject: Re: Looong update times on ARSCHEMA
**
How would that affect a form that isn't getting new inserts more than
occasionally? The nextId setting only affects
Size.
Guillaume
From: Action Request System discussion list(ARSList) [arslist@ARSLIST.ORG]
on behalf of Rick Cook [remedyr...@gmail.com]
Sent: Wednesday, June 08, 2011 11:49 AM
To: arslist@ARSLIST.ORG
Subject: Re: Looong update times on ARSCHEMA
) [arslist@ARSLIST.ORG] on
behalf of Rick Cook [remedyr...@gmail.com]
Sent: Wednesday, June 08, 2011 1:27 PM
To: arslist@ARSLIST.ORG
Subject: Re: Looong update times on ARSCHEMA
**
What I think we have is some confusion in terms. While the nextId value for
each form is stored
I see you have been afflicted with trusting the BMC sales...err...product
documentation on that feature. If you have real experience that shows
clearly that this makes a positive difference, I would love to hear about
it. I have significant experience with using this setting, and after our
data
Request System discussion list(ARSList) [arslist@ARSLIST.ORG] on
behalf of Rick Cook [remedyr...@gmail.com]
Sent: Wednesday, June 08, 2011 1:59 PM
To: arslist@ARSLIST.ORG
Subject: Re: Looong update times on ARSCHEMA
**
I see you have been afflicted with trusting the BMC sales...err...product
Listers...
I was helping a person who contacted me look at a performance problem.
I do not have access to the system.
It appears the update to ARSCHEMA that is called by the CE API call is
taking forever for just ONE record. In other words when this executes:
UPDATE arschema SET nextId =
databases.
HTH
Kind Regards Conny
Von: Action Request System discussion list(ARSList)
[mailto:arsl...@arslist.org] Im Auftrag von William Rentfrow
Gesendet: Mittwoch, 4. November 2009 19:39
An: arslist@ARSLIST.ORG
Betreff: Looong update times on ARSCHEMA
Of William Rentfrow
Sent: Wednesday, November 04, 2009 12:39 PM
To: arslist@ARSLIST.ORG
Subject: Looong update times on ARSCHEMA
**
Listers...
I was helping a person who contacted me look at a performance problem. I do
not have access to the system.
It appears the update to ARSCHEMA
I ran into a situation like this where that one form was the
Distributed Pending form. We had a situation where there were
three application servers initiating between 750k and 850k DSO
transactions a day. During peak times, the UPDATE ARSCHEMA SET nextId
= nextId + 1 WHERE schemaId =
12 matches
Mail list logo
