Tempdb is a ala temporary tablespace in sql server. AR installer does not 
create this. When SQL Server is installed the setup program creates tempdb 
database. Tempdb is a system database used by SQL Server to store temporary 
tables and temporary stored procedures, for sorting, subqueries, and aggregates 
with GROUP BY, ORDER BY, for cursors and so on. Tempdb database contains only 
temporary objects, so if you want to create a permanent object, do not create 
it in the tempdb database.

Regards,
Abhijeet
________________________________
From: Action Request System discussion list(ARSList) 
[mailto:[email protected]] On Behalf Of Robert Molenda
Sent: Saturday, May 23, 2009 6:47 PM
To: [email protected]
Subject: Re: Performance Tuning ARS 7.1

**
We have been experiancing random ARERR 92 / 8939's at several custom locations 
- generally a restart of ARS clears the issue - this is occuring on multiple 
7.1 patch versoins.

Since this is the 'tempdb' and not ARSystem - I am curious as to what ARS would 
be doing in the tempdb - guess I need to enable profiler and check the 
activity...

One question - is what is the transaction logsize of tempdb? is it attempting 
to grow (and grow)??

I will pass this 'tip' on to my team(s) for them to try at a few customer 
locations just to double check...
Robert Molenda
On Thu, May 21, 2009 at 11:43 AM, Leonard Nelson 
<[email protected]<mailto:[email protected]>> wrote:
Hello All

We just launched ARS 7.1 two weeks ago. Things have been running
fairly well until last week when we started to see the error "ARERR 92
Timeout during database update -- the operation has been accepted by
the server and will usually complete successfully : 
server.com<http://server.com/>"

With BMC guidance we increased the tempdb size from an initial 8MB to
1GB. The ARERR 92 error appeared to be resolved until earlier this
week when we started seeing error "ARERR 382 The value(s) for this
entry violate a unique index that has been defined for this form :
HPD:Help Desk entry:INC000000008832 fields:  " and error "ARERR 8939
The AR System Plug-In server is not responding. Cannot connect to the
system at this time. Contact your AR System Administrator for
assistance. : RPC: Timed out"

I suspect that ARERR 92 and ARERR 382 are related, so earlier this
morning I increased the tempdb size from 1GB to 5GB. This appears to
have resolved these errors. However, I'm not sure if ARERR 8939 is
related to this issue but restarting the arplugin.exe process appears
to have resolved this issue.

Our AR server is running on a Windows 2003 server R2 with 8GB RAM and
the database backed is SQL 2005 running on a similar server.

I'm curious if anyone else has encountered similar issues and what
recommendations people have for improving performance of a system.
Clearly, we are learning some new ways of tuning our system, so any
tips would be greatly appreciated.

Leo

_______________________________________________________________________________
UNSUBSCRIBE or access ARSlist Archives at 
www.arslist.org<http://www.arslist.org/>
Platinum 
Sponsor:[email protected]<mailto:sponsor%[email protected]> 
ARSlist: "Where the Answers Are"



--
If it were not for the gutter, my mind would be homeless!
_Platinum Sponsor: [email protected] ARSlist: "Where the Answers Are"_

_______________________________________________________________________________
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
Platinum Sponsor:[email protected] ARSlist: "Where the Answers Are"

Reply via email to