I have been using Nav 3.60 with a native db for years. We are about to install a completely new Nav solution using Nav5 and SQL 2005. The supplier has quoted for new hardware, but I am unsure why the supplier is quoting for a separate server to run Nav5 on.
I've read in the forums about the SQL server specs and performance and understand those needs, but not why you'd put Nav5 on a separate server.
We are looking at installing a solution for 70 concurrent users of which 10 will be remote users (using Citrix) and BI toolset. The client PC's are all XP and Vista.
The supplier has quoted the server solution below. Can anyone help with my lack of understanding.
NAV5 Server
HP ML370, 2GB ram, 1xDual Core, 2x80GB Hard Disks,
SQL Server
HP DL580, 16GB ram , 2xQuad Core,
Storage System
HP StorageWorks Smart Array 70 (12x72GB Raid)
Citrix Server
HP DL360, 4GB, 1xDual Core, 2x72.8GB Hard Disks,
BI Server
HP ML370, 2GB, 1xDual Core, 2x80GB Hard Disks
Thanks
0
Comments
Old situation:
- Server with native nas server service as running 3.70 db.
- clients had client 3.70 installed connecting to this server
New situation:
- SQL server runs sql 2005 with navision db
- clients have client 5.0 installed connection to sql db...
Seperate citrix for remote clients seems logical (clients on citrix connect to same sql server)
If you use cubes on sql for your bi, and your sql server is big enough, i even would not set a seperate BI server...
Benny Giebens
My personal feeling was what you've said. However, not knowing version 5 on SQL I thought I might be missing something obvious.
Thanks again.
For the BI server, assuming you are going to use SQL Server BI tools, did they also quote you for an additional instance of SQL Server? That is not a cheap solution that they gave you there.
RIS Plus, LLC
Problem is to find these and then convince the client to change...
When we do project and new hardware, we make an offer to check out hardware and install sql ourselfs...
So client chooses his hardware the way he likes, we only make a report with our recommendations on hardware (based on MS hardware sizing report).
If client chooses not to follow MS recomendations, we have a signed document so they can not come back to us later on the fact of wrong hardware ...
Benny Giebens
I've been on calls where customers asked for my advice, only to go 180 degrees in a different direction, completely dismissing what I had to add. It is difficult to argue when there is a "hardware specialist" that can talk "IT speak" and is spewing numbers that impress the customer.
You're right though, in those cases you must have some sort of documentation that the customer is not following your recommendations, or at least send them a letter warning them about possible issues they may face if they make those decisions. Of course including the fact that they will be billed in full when the problems do start.
RIS Plus, LLC
The supplier has quoted for a separate BI suite from a 3rd party supplier.
Is the Dynamics Business Analytics part of the SQL BI suite or is the SQL BI suite a separate product?
I would not run the NAS Server on the same server as the SQL ServeR. Why? The SQL Server is probably a 64 bit server, with 64bit Windows and 64 bit SQL Server (at least, I hope so, because of the 16Gb of RAM). Running 32 bit applications on 64 bit OS is not a good idea. It could affect performance. Always run NAS on a 32 bit server.
May be the vendor meant NAS server with the extra NAV5 Server?
Just a guess...
Eric Wauters
MVP - Microsoft Dynamics NAV
My blog
MVP - Dynamics NAV
My BLOG
NAVERTICA a.s.
The DL580 is a 4 socket server. Purchasing it with only 2 processors means you paying for chassis capacity you don't need. Dropping down to the DL385 would drop a chunk off the budget.
On the ML370s, why buy a chassis that hold 8 to 16 drives and only put 2 in it. Drop to a smaller chassis and use the money on your NAV install.
I will be the first to tell someone that they need the right hardware. But there is no reason to over-purchase.
I agree, it does look like just a terminology issue.
Still that machine maybe an over kill for NAS though. But like Eric says don't run NAS on your SQL server.