This was a database copied from a dev server to another instance of another
dev environment we are attempting to bring up to conduct another development
path so the two tracks do not overlap. So there was nothing (no Remedy
instance or any other process that I am aware of) connected to that database
instance.

Thanks for your suggestion. That query for some reason took over 7 hours to
execute - it did eventually complete successfully. I have never had it take
that long on me. I would need to check with the DBA what was causing it to
take that long. My initial suspicion is possible inadequate resources on
their database servers in the dev pool..

Joe

-----Original Message-----
From: Action Request System discussion list(ARSList)
[mailto:[email protected]] On Behalf Of Longwing, LJ CTR MDA/IC
Sent: Wednesday, January 02, 2013 10:28 AM
To: [email protected]
Subject: Re: Configuration tasks to avoid deadlocks on MS-SQL 2008...

Joe,
Remedy can't be running when you execute that one...so, shut it down if you
didn't already.

-----Original Message-----
From: Action Request System discussion list(ARSList)
[mailto:[email protected]] On Behalf Of Joe D'Souza
Sent: Monday, December 31, 2012 4:54 AM
To: [email protected]
Subject: Re: Configuration tasks to avoid deadlocks on MS-SQL 2008...

** 

 

Ignore this request.. I found the documentation. Now only if I could get one
of the queries to actually complete execution! I think something is wrong
with it as its taking forever to execute it.. Over 5 hours now. And I do not
recall it ever taking over 2 seconds to complete..

 

The one that seems to be 'stuck' is

 

ALTER DATABASE ARSystem SET READ_COMMITED_SNAPSHOT ON;

 

Its 5 hrs 17 minutes now and still displaying Executing query in the status
bar..

 

Has anyone had trouble with this one before?

 

Joe

 

________________________________

From: Joe D'Souza [mailto:[email protected]] 
Sent: Monday, December 31, 2012 1:22 AM
To: ARS Discussion List
Subject: Configuration tasks to avoid deadlocks on MS-SQL 2008...

 

 

How do you implement the NOLOCK configuration on an MS-SQL database? I
recall doing this in the past, using hints on the installation document of
the AR System server. But I can't seem to be able to find the installation
document.

 

This is the prompt that you get when installing AR System 7.6.04, which
requires the DB to be set to NOLOCK..

 

When installing or upgrading on Microsoft SQL Server 2005 or higher,
Microsoft recommends that you perform additional configuration tasks to
avoid deadlocks. Please refer to the AR System Installation Guide in the
"Additional Procedure for preparing a SQL Server database" for more
information.

 

Any help on this will be appreciated.

 

Joe

_ARSlist: "Where the Answers Are" and have been for 20 years_ 

____________________________________________________________________________
___
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
"Where the Answers Are, and have been for 20 years"

_______________________________________________________________________________
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
"Where the Answers Are, and have been for 20 years"

Reply via email to