I will be very interested to learn if this was a hardware problem, since my management is insisting that I move from HP to Dell hardware. I have not seen any problems with our SQL Server 2005 SP2 x64 (Standard) db, but after 5 months in production the ARSystem db is still only 4.3 gb in size. We have 162,680 defined customers, but historically our ticket volume is comparatively light - I only had to move 100,000 archived tickets from the 5.x system to 7, which was everything entered after our first 3.x system went live in 1998. That is growing now that we are on 7.x and have a better self-service portal in Kinetic Request, but I only have 300 support staff and some of the support areas are very light users.
Christopher Strauss, Ph.D. Call Tracking Administration Manager University of North Texas Computing & IT Center http://itsm.unt.edu/ From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of Jeff Lockemy (Northrop Grumman Mission Systems) Sent: Sunday, October 12, 2008 10:37 AM To: arslist@ARSLIST.ORG Subject: Re: Production SQL Server Problem ** Well, we have SQL Server 2005 running with a restored copy of the 45GB ARSystem database on a DELL PowerEdge 1950. It is looking good. So I suspect that the problem may be with the PowerEdge 2850. Perhaps the way that the system or RAID does caching. Who knows. I'm keeping my fingers crossed. From: Jeff Lockemy (Northrop Grumman Mission Systems) [mailto:[EMAIL PROTECTED] Sent: Saturday, October 11, 2008 12:15 PM To: 'arslist@ARSLIST.ORG' Subject: RE: Production SQL Server Problem Hi Rick, We haven't gone back to a previous back-up yet. We do have SQL 2005 pretty much running bare as we can. I have DTS working on pulling data out of one restore of the database, to see if I can rebuild a new database fresh (to eliminate database corruption as being a culprit). I also have another restore on a different type of hardware that I am going to try to get Remedy online with to dump some of the key tables from another copy of the restore. My key concern right now is the data, then I can tackle getting things rebuilt, back online and service restored. Mainly was looking to see if anyone knew of any known issues with SQL Server 2005. But I appreciate any suggestions... Best regards, Jeff From: Action Request System discussion list(ARSList) [mailto:[EMAIL PROTECTED] On Behalf Of Rick Cook Sent: Saturday, October 11, 2008 11:49 AM To: arslist@ARSLIST.ORG Subject: Re: Production SQL Server Problem ** Maybe not - the times I've seen that are when a DB action is taken against the DB row containing the problem. I suppose an index build or rebuild might be a potential trigger, if that's the real problem, but that's grasping a bit. Is it possible to bring the DB online a piece at a time, or with selected features turned off? Do previous backups have the same problem? Rick On Sat, Oct 11, 2008 at 11:41 AM, Jeff Lockemy (Northrop Grumman Mission Systems) <[EMAIL PROTECTED]<mailto:[EMAIL PROTECTED]>> wrote: ** Hi Rick, Thank you for the response. This all happens before we even bring the AR System application online. Do you think it could still be that? Regards, Jeff From: Action Request System discussion list(ARSList) [mailto:arslist@ARSLIST.ORG<mailto:arslist@ARSLIST.ORG>] On Behalf Of Rick Cook Sent: Saturday, October 11, 2008 11:17 AM To: arslist@ARSLIST.ORG<mailto:arslist@ARSLIST.ORG> Subject: Re: Production SQL Server Problem ** Jeff, turn on your SQL logs next time you put it on line - it may point to a workflow or data issue (i.e. a field overflow) that's causing this. I've seen that happen. Rick On Sat, Oct 11, 2008 at 10:56 AM, Jeff Lockemy (Northrop Grumman Mission Systems) <[EMAIL PROTECTED]<mailto:[EMAIL PROTECTED]>> wrote: ** Listers! We have a problem with a production SQL Database Server. We are running SQL Server 2005 Enterprise Edition SP2 on Windows Server 2003 Enterprise Edition SP2, on a Dell PowerEdge 2850. When we bring our ARSystem database online (45GB), it may run for a while but then without warning the system will lock-up, then blue screen and reboot. After the reboot, the database is corrupt and must be restored again from back-up. We have ensured that all of our drivers and firmware are up-to-date on the servers, and are staging a different PowerEdge model to eliminate the 2850 server hardware as being suspect. At this point we still don't know if it is a O/S, SQL Server, database or system problem. Has anyone seen any problems like this with SQL 2005? Any suggestions on where else we might look? Thanks in advance... Jeff Jeff Lockemy QMX Support Services __Platinum Sponsor: www.rmsportal.com<http://www.rmsportal.com> ARSlist: "Where the Answers Are" html___ __Platinum Sponsor: www.rmsportal.com<http://www.rmsportal.com> ARSlist: "Where the Answers Are" html___ __Platinum Sponsor: www.rmsportal.com<http://www.rmsportal.com> ARSlist: "Where the Answers Are" html___ __Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are" html___ __Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are" html___ _______________________________________________________________________________ UNSUBSCRIBE or access ARSlist Archives at www.arslist.org Platinum Sponsor: www.rmsportal.com ARSlist: "Where the Answers Are"
