You do NOT want to try to convert a 2008 db back to 2005. The one time I tried that (yes, there was a documented way to do it - probably in TechNet) it more than doubled the size of the db files and refused to be shrunk afterwards. You may have different experience, but mine was all bad.
My sample data 7.6.04.01 system is on three Win2K8 server VMs (SQL 2008, ARS, MidTier) with inadequate horsepower, and you are correct - it is slow. It is only useful for looking at OOTB functions and objects as a reference. Christopher Strauss, Ph.D. Call Tracking Administration Manager University of North Texas Computing & IT Center http://itsm.unt.edu/ -----Original Message----- From: Action Request System discussion list(ARSList) [mailto:[email protected]] On Behalf Of Larry Barnes Sent: Wednesday, July 20, 2011 10:22 AM To: [email protected] Subject: Migration in reverse I have a development server running ITSM 7.6.04 on a VM with 8 gig of ram and is running SQL 2008 on a separate server. We are dealing with slowness with ITSM and I'm not sure where the bottle neck is. We are running (64 bit) Tomcat and Java; latest releases. Java has an Initial memory pool of 512 MB and a maximum memory pool of 2048 MB and the Thread stack size is 4096 KB. I may need to move the SQL db off of the 2008 box and place it on a SQL cluster that is running SQL 2005. Does anyone know of issues with moving back to 2005 from 2008? Thanks for checking, Larry B. _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug11 www.wwrug.com ARSList: "Where the Answers Are" _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org attend wwrug11 www.wwrug.com ARSList: "Where the Answers Are"
