Hello,
we migrate an application from old to new hardware. In this step we migrate
also from SQL Server 2000 SP 2 on a Windows 2000 Server to SQL Server 2000
SP 4 on a Windows 2003 Server. Because of the new hardware almost every job
on the database ist much faster (up to 3 and 4 times) than before except one
job.
This job is recalculating values in the database. The job starts a stored
procedure which opens a transaction. In this transaction there is a loop
over a large amount of entries. For each entry another stored procedure is
called to recalculate the values. This stored procedure is also covered in a
transaction. The inner stored procedures does some insertions and updates.
On the old system the recalculations are done on a constant rate. On the new
system the recalculation rate degrades on a factor of 10 % every minute. So
the complete job lasts almost four times as long on the new system, although
the beginning rate of the calculations is much higher on the new system. The
problem is that this job now takes about 8 hours to complete so we cannot
reconfigure our system during the night any more.
We did a lot of testing and changes about this issue like database
maintenance (recalculation of indices, reorganisation of indices etc.) and
changes of the configuration (enlarge the transaction log files of the
database and the temp.db).
The issue occure on different systems with different configurations and is
not hardware dependent. It seems to be a problem in the combination of SQL
Server 2000 and Windows 2003.
Are there any suggestions about this issue?
Best Regards
Harald Gehringhttp://support.microsoft.com/kb/899...2852&sid=global
Please check the stored procedure / TSQL to check if you are running into
the above issue.
Tuesday, March 20, 2012
Performance Problem on SQL Server 2000 SP 4 on Win2003
Labels:
application,
database,
hardware,
microsoft,
migrate,
migratealso,
mysql,
old,
oracle,
performance,
server,
sql,
step,
win2003,
windows
Subscribe to:
Post Comments (Atom)
No comments:
Post a Comment