SQL Server Cofiguration

SBN

Hello Experts,

I am running Navision 5.0. Over the past few months, it has been running very slow.
I am going to make a new configuration of the db Server in order to resolve make it running quickly.

Data Base Info:
Database Used (KB): 38,810,624 (47%)
Database Size (KB): 81,960,960
With licence of 30 users.


Server Specs:
Processor: Two processors Intel Xeon 2.5GHz Quad Core
RAM: 8 GB
Disks: 8 physical disks x 176GB
Two disks with RAID1+0 For OS+SQL
Two disks with RAID1+0 For LOG
Four disks with RAID1+0 For DATA



Windows Server 2003 R2 Enterprise E 64-Bit
SQL Server 2005 Standard E 64-Bit

We are accessing directly, and for the distant site, we are using Terminal Server on another server.

What about this new config, it resolves a part of the problem or not?

Thanks in advance

kriki

The hardware+software configuration is ok.
But it also depends on how you configure that. You need to align the disks correctly (offset = multiple of 64KB, sector size=64KB, stripesize (for RAID10) = 64KB).
Between your SQL server and terminal server, you best have a 1Gbit connection.

Be sure you don't have fragmentation on your disks.
Be sure your TL-file doesn't have internal fragmentation.

Also a lot of other things can be done.
I suppose you use 5.0 without SP1. In this case you need to do some index/SIFT tuning.

Search the forum for more details. There is a lot you can find.

SBN

Thank you Kriki,
:thumbsup:
We have 8GB memory installed on the server,and when I execute task manager it shows that all of this memory is used,specialy 7.4 is used by SQL process,is it normal ?
The extesion of memory can be better ?

Thanks for help

kriki

For most implementations, 8GB of memory is enough for that size of DB.
It is normal that SQL uses most of the memory. Actually,this SHOULD be the case in a dedicated server (and a server SHOULD be dedicated to SQL server).

SBN

How can I find that the TL-file has internal fragmentation or not?
When I create a new database I fixed the size of log file =2.5GO ,I put the recovery model to "Simple" and I
define a daily sql maintenance plan (Full backup,Reorganise+Rebuild indexes,Update statistics).
This config is better or Full recovery model with bakup of TL file???

stryk

Hi!

Well, first of all I suggest that you search MIBUSO for "SQL Performance" - as this is a permanently discussed issue you'll get gazillions of advices and recommendations!

As Kriki said, the platform seems sufficent enough, but this also depends on the transaction volume you process. With NAV 5.0 (which version exactly?) you could be sure it is the application itself which causes most (all?) of that trouble ...

Reagrding the "Recovery Model": WIth SIMPLE the Log is immediately truncated when a transaction is committed, hence the Log is just used temporary. This actually should keep it quite small. But you are waiving the possibility to create Log Backups:
With FULL Recovery all transaction info remains in the Log until Log Backups was created; thus you HAVE to run Log-Backups to keep its size reasonable. The big advantage is, that with Log Backups you could restore the database up to the latest transactions, hence your potentialdata-loss in worst case is minimal.
See "Books Online" about details.

Maybe this one could also help you.

Best regards,
Jörg

stryk

SBN wrote:

How can I find that the TL-file has internal fragmentation or not?

Ups, forgot that one ...
You could check with DBCC LOGINFO. The amount of lines tells the number of VLogs, the "internal/logical fragments" so to speak. Should be something between 16 and 64.

SBN

Hello stryk,
Thank you for the reply,about our activity we are medical product distributor,so a lot of transactions per day :AVG = 7000 entries per day
I am going to by 8GB of memory for an extesion,what is your advice about that?

Thanks in advance

kriki

SBN wrote:

How can I find that the TL-file has internal fragmentation or not?

Here is more info on how to see and fix it: http://mibuso.com/blogs/kriki/2008/12/23/some-tips-tricks-for-the-transaction-log/

stryk

SBN wrote:

Hello stryk,
Thank you for the reply,about our activity we are medical product distributor,so a lot of transactions per day :AVG = 7000 entries per day
I am going to by 8GB of memory for an extesion,what is your advice about that?

Thanks in advance

Well, according to the "NAV Hardware Sizing Guide" 8GB RAM with a DB up to 40GB (used size) and 50 to 150 users should be OK. I - personally - consider 8GB as absolute minimum with SQL Server, else sooner or later you might encounter trouble. Have in mind that your database will continously grow, tables will get larger, hence the size of indexes is increasing. So depending on the business processes and the queries which are executed, the "logical I/O" will increase (thus causing perf-issues) with growing of the tables & indexes. If not enough RAM is available, this "logical I/O" will result in "physical I/O" which slows the system further down.
Also, certain user interactions - filters, wildcards, etc. - will generate queries which result in pretty high I/O ...

To make a long story short: the more RAM you have, the more data could be cached, the less physical access is necessary. Also, plenty of RAM makes the system more "forgiving" to bad queries ...

RAM doesn't cost a fortune anymore, so if you could afford it I'd go for 16GB+ ... the more the better.

davmac1

RAM overcomes a lot of problems. I inherited a SQL Server NAV 5 SP1 customer with a RAID 5 system and the performance was bad at times. We bumped it up to 12 GB and the performance problems went away.
They only had about 20 concurrent users which is probably why the quick fix worked.