Rick:
Sometimes it does, sometimes it does not. I would not recommend putting the server in development mode to do a data load up.
James Mckenzie
-----Original Message-----
From: Action Request System discussion list(ARSList) [mailto:[email protected]] On Behalf Of Rick Cook
Sent: Thursday, July 20, 2006 7:48 AM
To: [email protected]
Subject: Re: ITSM 7 - Installation
I have heard that putting the server in Development Cache Mode also helps with performance during installation and migration. I haven't done full testing on that, though.
Rick
-----Original Message-----
From: Action Request System discussion list(ARSList) [mailto:[email protected]] On Behalf Of Mike Parker
Sent: Thursday, July 20, 2006 6:47 AM
To: [email protected]
Subject: Re: ITSM 7 - Installation
Hi Mary:
In addition to the threads, I also did the following:
1) Disabled Escalations from the Admin tool
2) Disable any non-essential processes (email engine, flashboards server,
etc)
Incident & Problem went on without a hitch then. Both took about 3 hours.
I just started Change so we'll see what happens then.
>From: "McKenzie, James J C-E LCMC HQISEC/L3"
><[EMAIL PROTECTED]>
>Reply-To: [email protected]
>To: [email protected]
>Subject: Re: ITSM 7 - Installation
>Date: Thu, 20 Jul 2006 06:41:41 -0700
>
>Mary:
>
>You need at least 4 threads for fast and list servers. This is true
>for any of the CMDB installations (CMDB 1.1 will 'crash' if you don't
>have enough threads running.)
>
>James McKenzie
>
>-----Original Message-----
>From: Action Request System discussion list(ARSList)
>[mailto:[email protected]] On Behalf Of Mary C.
>Sent: Wednesday, July 19, 2006 5:46 PM
>To: [email protected]
>Subject: Re: ITSM 7 - Installation
>
>Wow, your Incident install took 1 hour? My install took 6 hours on 1
>server and 9 hours on another server. (It was the 1st app I installed
>in the ITSM suite, so therefore, Financial Management and all the other
>common apps had to be installed). I thought it hung, but fortunately I
>checked SQL activity, and it was busy creating records and objects,
>etc.
>
>The good news is the successive app installs went way faster (1 to 2
>hours each).
>
>Our hardware meets the min. requirements (barely). I began the install
>by backing up the database and truncating the trans. log. I also
>increased the trans. log file size.
>
>We're on Windows 2003 on a virtual machine (ESX server) & SQL 2000 on a
>remote server.
>
>I didn't see anything in the pre-reqs. about multi-threading settings.
>Where was that? Any other advice on how to cut down on install time?
>
>_______________________________________________________________________
>_____
>___
>UNSUBSCRIBE or access ARSlist Archives at http://www.wwrug.org
>
>_______________________________________________________________________
>________ UNSUBSCRIBE or access ARSlist Archives at http://www.wwrug.org
_________________________________________________________________
Express yourself instantly with MSN Messenger! Download today - it's FREE!
http://messenger.msn.click-url.com/go/onm00200471ave/direct/01/
________________________________________________________________________
_______
UNSUBSCRIBE or access ARSlist Archives at http://www.wwrug.org
_______________________________________________________________________________
UNSUBSCRIBE or access ARSlist Archives at http://www.wwrug.org
