May 27, 2002 at 5:42 am
We've upgraded from SQL7 to SQL2k (Sp2) on our production server over the weekend and have a problem with cube processing. When processing our cubes, the job hangs just after the initialization of the cube's partition. It hangs for exactly 1 hour, then returns a timeout error. Not trusting the upgrade process, I uninstalled SQL Server 2000 (and deleted any remnants of SQL7 left on the server), and reinstalled SQL2k and SP2. Now it's a little better - the job still hangs at the same spot for exactly 1 hour, but then instead of a timeout error, it continues processing and is successful.
This particular cube normally processes in 13 minutes before the upgrade. We performed the upgrade on two test servers (one single processor P4-1.5Ghz and one single processor P3-550) and both upgrades were successful. No problems in processing the cubes. The only difference for production server is that it is a 4 processor P3-550.
Any ideas out there? Thanks...
August 18, 2002 at 11:37 am
Did you ever find the cause of the problem? If so, what did you have to do to resolve it?
Thank you,
Michael
Michael Weiss
Michael Weiss
September 2, 2002 at 1:54 am
Hi, back from vacation, sorry for the lack of reply. Basically, there was no hang anymore, the query was just taking much longer for some reason after the upgrade. After much investigation and tuning, I was able to get the total query time down to something around 20minutes. Still, a long ways off from the original 13 minutes. It appears the source of the problem is not SQL2k, but the 4x processors. We have two test servers, both with 1x processor, which have had no problems.
September 2, 2002 at 5:08 am
Don't know if it is of any use, but there have been some threads a while back about multi-processor systems having problems.
Maybe you can check those for a possible cause or solution.
Viewing 4 posts - 1 through 3 (of 3 total)
You must be logged in to reply to this topic. Login to reply