NAV5 and SQL2005

Auke

At our company we have a customer that has a native 2.60 database with a database size of 50Gb.

We have started a project to upgrate them to NAV5 an SQL2005.

Now Microsoft said that SQL 2005 x64 is the best option.
The customer asked me the following questions:
- which Operating system is the best for us?
- How should the RAID and the size of the disk be?
- Wich formula do we need to handle for calculate the disk for the log-files.

The database now expands with 10GB a year (native) I think for SQL that wil be more.

Does anyone has an answer for me?

Thanks

Auke

garak

if you will use SQL Server x64, u need an Win Server 2003 x64.

• Standard: Single(1) - Quad(4)-Prozessor-Systeme up to 32 GB RAM
• Enterprise: Single(1) - Oct( 8 )-Prozessor-Systeme up to 1 TB RAM
• Datacenter: Oct( 8 ) - 64-Prozessor-Systeme up to 1 TB RAM

Wich Raid, mhm here my fist shut, these would i use when using big databases.

RAID 1 for HDD with OS
RAID 1 for HDD with master, model, msdb
RAID 1 for HDD with tempDB
RAID 10 for HDDs with mdf / ndf
RAID 10 for HDDs with ldf

Please read also the Database_Resource_Kit.pdf on CD

Waldo

Definitely go for x64 and enough RAM for rowlocking (8 to 16Gb).

If you have enough budget, go for garak's proposal. The minimum should be:
RAID 1 for OS
RAID 1 for TL
RAID 10 for database

Be sure to set the right server and database settings. And set up the maintenance!

bbrown

A few comments:

1. Separate the mdf and ndf files onto different drives. The mdf can share the drive with master, model, msdb. This won't do much for performance but it provides an extra layer of posssible recovery.

2. On the RAID 10 for the ndf file, the number of physical drives is more important then the size.

Auke

Thanks.

@Garak: I do not have the Database_Resource_Kit.pdf on my cd

garak

Hi if you are an partner than go to this page

https://mbs.microsoft.com/partnersource ... page=false

Here you can find all Navision Tools and the resource Kit

garak

Another note: Do not only migrate your database.
Search through your code, SIFTs, Indexes, table structure and optimize it for SQL. If you optimize these things, your sql database will run like (it's eastern) a rabbit.

Examples for this you can also find in the PDf or under SQL Perfomance in this wunderfully, helpfully forum.