MarshallB
Well Known Member
We have recently added a database server to our JDE architecture. We
went from one 2 processor Windows enterprise server (database and
Logic), and now have split it between a logic and database server. So
now we have Logic on a dual proc machine, and the database on a 4 proc
machine, and we have seen significant performance improvements.
Essentially all daily processing is considerably faster, order entry,
picking, packing etc... it's all going great. The odd thing is some of
our long running reports have begun running even longer. For example
the R41543 Item Ledger/Account Integrity ran for an additional 5 hours
this past weekend! I realize that the data has to move across the
network between the two servers now (which is a gigabit connection), but
that seems like an extremely long time.
Servers:
Database
Win2k3 server, SQL Server 2000 standard sp3, 4 xeon 3.0 ghz procs
(hyperthreading ON), 4 gb RAM
Logic
Win2K server, 2 xeon 1.9 ghz procs (hyperthreading off), 4gb RAM
I had read earlier that you want to turn hyperthreading off for SQL.
But the latest info I could find had shown Windows server 2003, and SQL
server 2000 SP3 were able to take full advantage of hyperthreading and
it should be left on.
Has anyone seen this before? I appreciate any ideas.
Marshall Baird
Senior Systems Support Specialist
Weaver Leather, INC.
330.674.7548 ex.153
[email protected]
went from one 2 processor Windows enterprise server (database and
Logic), and now have split it between a logic and database server. So
now we have Logic on a dual proc machine, and the database on a 4 proc
machine, and we have seen significant performance improvements.
Essentially all daily processing is considerably faster, order entry,
picking, packing etc... it's all going great. The odd thing is some of
our long running reports have begun running even longer. For example
the R41543 Item Ledger/Account Integrity ran for an additional 5 hours
this past weekend! I realize that the data has to move across the
network between the two servers now (which is a gigabit connection), but
that seems like an extremely long time.
Servers:
Database
Win2k3 server, SQL Server 2000 standard sp3, 4 xeon 3.0 ghz procs
(hyperthreading ON), 4 gb RAM
Logic
Win2K server, 2 xeon 1.9 ghz procs (hyperthreading off), 4gb RAM
I had read earlier that you want to turn hyperthreading off for SQL.
But the latest info I could find had shown Windows server 2003, and SQL
server 2000 SP3 were able to take full advantage of hyperthreading and
it should be left on.
Has anyone seen this before? I appreciate any ideas.
Marshall Baird
Senior Systems Support Specialist
Weaver Leather, INC.
330.674.7548 ex.153
[email protected]