CNC

thejdofva

Member
Hi All
Following is the picture of my CNC:

DEPLOYMENT SERVER:
Windows 2000 sp4
ENTERPRISE SERVER:
Window 2000 sp4, Sql 2000 Sp3a with SAN. Production and the system database resides on the server dirve (D:), all other databases are on the SAN (E:).
CITRIX SERVER:
Windows 2003 Standard Edition SP2

Things are running fine with nominal issues here and there. A suggestion was made to the higher uppers to add another server and put all the databases on that server (separate databse server).

I think my setup right now is better then having a database on a different server. I would like to know you'alls opinion . If the above suggestion is a better then I'll be happy to make the change otherwise why bother.

Thanx in advance.
 
Hi,

From a short term vision, I'd say : "If everything is
going OK, then why change it?"

However, from a long term vision, putting database and
applications on the same server is not a scalable solution.

SQL and JDE compete for memory, CPU and disk resources;
often stealing resources each other.

Finally, you should also be thinking about separating
Production from Development databases, from both
security and performance points of view.

Regards,
 
From my experience, they do not really compete, because DB mostly uses disk and memory, while JDE - CPU.

Every time I tested UBE performance, they would perform better on the shared server, compared to a dedicated one, even if the shared server was a bit slower. The small overhead of the network in between seems to have a noticeable effect...

Scalability would suffer somewhat, that's true.
 
Well there are 2 schiils of though here:

(1) If it ain't broke then don't try and fix it.
-Since you don't have any issues then why change anything?
-Having a single server is easy to manage and is used in the majority of JDE impltmentations.
-1000 GB is great but zero latency is better (combined server)
-for a small number of users there is no reason to add more hardware and just to have 2 servers running at 10% CPU utilization when you can one server running at 15%
-instead of investing in more hardware put everything on one server and get a SAN. Given the choice I go for the SAN

(2) Separation is good
-yes in some cases because th DB does different things from JDE
-for very large customers this is the way to go

of the 150+ JDE clients ou company supports about 5% have a seperate database server.

I'm actualy now consolidating a client that has 2 servers (1 CPU Enterprise server - non HT with 4 GB RAM and a 2 CPU DB SQL Server 2K- HT with 4 GB RAM) to a single piece of hardware: 4 way dual core - HT with 16 GB RAM on SQL Server 2005.


Colin
 
[ QUOTE ]
Hi All
Following is the picture of my CNC:

[/ QUOTE ]

Attached is a picture of my CNC.
 

Attachments

  • 120534-IMG_1925_Cropped.jpg
    120534-IMG_1925_Cropped.jpg
    230.4 KB · Views: 228
LOL
grin.gif
grin.gif
grin.gif


Thats an ugly architecture right there...
 
[ QUOTE ]
LOL
grin.gif
grin.gif
grin.gif


Thats an ugly architecture right there...

[/ QUOTE ]

I'll pass that along to my buddy, he'll be the one approaching the podium at your next presentation
smile.gif
 
[ QUOTE ]
[ QUOTE ]
Hi All
Following is the picture of my CNC:

[/ QUOTE ]

Attached is a picture of my CNC.

[/ QUOTE ]

Umm Jeff? This is JDElist.com, not e-harmony.com. I know it's easy to get the two mixed up.
grin.gif
 
I would like take a moment to say that Jeff's response should be in the running for "Funniest of 2007".

Also, here is a picture of my CNC (see attachment).
 

Attachments

  • 120549-CNC.jpg
    120549-CNC.jpg
    21.5 KB · Views: 210
Charles,

I second the motion. Jeff owes me a new keyboard, I spewed coffee all over this one....
 
ok - back to your original post. Why create a seperate appication server/database server architecture as opposed to the "virtual 3-tier" enterprise server model.

Really, the only compelling reason to do this is scalability and redundancy. If your enterprise is working fine with a single enterprise server, and you're not looking to add new users, functionality or change the way anything works - then don't change it !

However, if you're still adding functionality and users, and you start seeing that the enterprise server is becoming much more highly utilized - from a CPU perspective or from a memory perspective (paging) - then you might want to consider moving the applications to another server.

This allows you to do a couple of things :

1. Tune the database server AS a database server 100% - without the applications sitting on the box, it is now a pure database server
2. Use technologies that might not have been previously possible or difficult to use, such as database clustering, failover etc
3. Add additional application servers to your farm, providing higher scalability for your users and more redundancy from that level of the application

Certainly by moving application server part off onto another box, you start to become more "network bound" - but now you can start architecting the network to work in your advantage. Using gigabit ethernet to address the database server on different IP's for example - providing much higher throughput.

Secondly, the way that the kernel and listener processes work is similar to a traffic light on an entrance to a speeding highway - I think I've explained this analogy several times before - but to keep the flow of traffic moving, having the listener now control the messages to the kernels will dramatically increase scalability without necessarily impacting the database too much.

Lastly, by moving the application server onto another box, you can start to mix different operating systems - for example, use 64bit SQL 2005 as the database server, and yet use 32 bit windows as the application server - or use linux as application servers and HP9000 as your database server.

However - reading your original post, it sounds like your business is trying to reduce costs by placing the JDE database onto a "central" database server with lots of other databases on it. That is not a good move. When JDE is running, millions of SQL statements an hour/day is sent through to a database server - but other applications might not see anywhere near the level of SQL transactions that JDE provides. That would not reduce costs - and I'd want to fully understand the architecture your company is proposing.
 
[ QUOTE ]
[ QUOTE ]
[ QUOTE ]
Hi All
Following is the picture of my CNC:

[/ QUOTE ]

Attached is a picture of my CNC.

[/ QUOTE ]

Umm Jeff? This is JDElist.com, not e-harmony.com. I know it's easy to get the two mixed up.
grin.gif


[/ QUOTE ]

cool.gif


BTW, that is not me.....I am just as ugly but do have hair. Not that there's anything wrong with not having hair, I'm just saying.
 
Please pardon me. I am a new user to JDEList and I an trying to configure
my news groups so I can post and reply to questions on JDEList. However, I
am being prompt for NNTP server and I do not know what the NNTP server is.
Can you help me?

Thanks,

DDAUGHEN




_____

From: [email protected] [mailto:[email protected]] On
Behalf Of altquark
Sent: Friday, May 11, 2007 8:39 AM
To: [email protected]
Subject: Re: CNC


LOL <http://www.jdelist.com/ubb/images/graemlins/grin.gif>

Thats an ugly architecture right there...

Jon Steel EnterpriseOne Technical Specialist erpSOURCING LLC
http://www.erpsourcing.com [email protected] 24/7 Assistance - (904) 382 5701



_____


The entire <http://www.jdelist.com/ubb/showflat.php?Cat=&Board=> JDELIST
thread is available for viewing.


Looking for a job? Check out the Job


This is the JDELIST EnterpriseOne Mailing List.
JDELIST is not affiliated with JDEdwardsR.

To unsubscribe from this list via email, Click <mailto:
[email protected]?Subject=Unsubscribe&Body=Sirs,

Please remove
this address from the JDELIST EnterpriseOne Mailing List.

Thank You.>
here.
 
Back
Top