Scalablility for windows and SQL platforms

knoxjr

knoxjr

Member
Hello List,
Working with a client who is looking for some confirmation their acquired windows/SQL platform and E1 product is scalable to support their construction business with up to 1,000 concurrent users. Current installed is E812/TR8.96 on W2K3/SQL2005/and WAS 6.0 New owner wants to continue with E1, but has concerns that windows (and SQL 2005)platform will not scale to handle their future load, and are thinking they should maybe look to move to windows/oracle and/or AS400/DB2 (ya I know). Current configuration has dedicated data base, logic, batch, and JAS servers.

Client would like to know if there are any other JDE customers who have implemented E1, any version, on a windows/SQL platform whose business is construction, with yearly revenue is in the 5 – 10 billion range. This business has a relatively limited number of transactions per days, so it would also be helpful to hear from customers who may have smaller revenue, but have a higher number of transactions.

In best case, the client is looking a reference who can help verify that their current platform and product is scalable to support their construction business.

As always, appreciate your feedback and insights.
 
Jerry,

Praxair is on a windows 2003/SQL 2000 environment (currently looking at SQL 2005). We have seperate logic and batch servers and support over 3800 users and a high volume of transactions. Our Brazilian division has over 5000 users using a similiar environment other than the enterprise server which is Unix and Oracle. We are a manufacturer, but we also do a whole lot of plant construction.

Gregg Larkin
Praxair CNC
[email protected]
 
You didn't mention how many of your 3800 users are concurrent (poster mentioned 1000 concurrent users), and what "a high volume of transactions" means relative to the EnterpriseOne customer average (which is what?)
 
You mentioned individual servers for each component, so if the customer updates to Tools 8.96.2.0, they can support SQL Server 2005 on Windows x64, which means they should not run into the same scalability issues they could potentially run into with 32-bit SQL Server.
 
Charles,

During the day - about 400 concurrent. Our database grows about 10 gig a month.
 
1000 concurrent is pretty large, though it really depends on what type of functionality the users are going to be using. If you're talking 1000 sales order entry clerks - then its going to be challenging to scale no matter what architecture is chosen. However, if you're talking 1000 self service customers - thats a completely different functional load.

SQL 2000 is perfectly scalable - and SQL2005 is even more scalable than before. I know of many 500 concurrent user implementations under SQL2000, and I wouldn't see any major issues scaling substantially higher than that. It all depends on the architecture of the hardware that is chosen.

Traditionally, Oracle on Unix is the mainstay of the larger implementations. However, that doesn't necessarily mean that Oracle is the perfect choice for your organization.

EnterpriseOne will scale to "insane" numbers of users if the technology architecture is properly configured.
 
Back
Top