database size?

aliennav

what is the maximum database size irrespective of the hard disk size available,when using navision native database,not the sql one.
also tell me that bin how many partitions the database can be broken into?
Thanx in advance

kriki

Officially 128GB.
Exceptionally Microsoft can go to 256GB (or maybe also to 512GB).
You can divide the DB in maximum 16 partitions. Preferably 1 per physical RAID1 for performance.

aliennav

kriki wrote:

Officially 128GB.
Exceptionally Microsoft can go to 256GB (or maybe also to 512GB).
You can divide the DB in maximum 16 partitions. Preferably 1 per physical RAID1 for performance.

And how r officially and exceptionally differentiated?/
I mean in what scenario its 128/256/512?

Waldo

kriki wrote:

Officially 128GB.
Exceptionally Microsoft can go to 256GB (or maybe also to 512GB).
You can divide the DB in maximum 16 partitions. Preferably 1 per physical RAID1 for performance.

In addition:
All files should have an equal size ... .
When you create a new file on a new disk, it's best to do a backup/restore to re-organize the files.

kriki

aliennav wrote:

kriki wrote:

Officially 128GB.
Exceptionally Microsoft can go to 256GB (or maybe also to 512GB).
You can divide the DB in maximum 16 partitions. Preferably 1 per physical RAID1 for performance.

And how r officially and exceptionally differentiated?/
I mean in what scenario its 128/256/512?

Well, the only thing I know is that you have to ask it specifically.

kriki

Waldo wrote:

kriki wrote:

Officially 128GB.
Exceptionally Microsoft can go to 256GB (or maybe also to 512GB).
You can divide the DB in maximum 16 partitions. Preferably 1 per physical RAID1 for performance.

In addition:
All files should have an equal size ... .
When you create a new file on a new disk, it's best to do a backup/restore to re-organize the files.

Not really needed. The Navision DB takes care of that automatically.
Remember that in the Navision DB, a modify of a record in reality is a kind of insert because of Navision's version principle=>It 'inserts' a new instance of the record and when the transaction is commited it 'deletes' the old version.
In this way, Navision also starts to use the new file.

Waldo

Yes, I know that ... but the new file will be empty ... en that's why you're going to write only in the new file until it's equally filled. Only then it's going to enjoy the division of all files. That's why I would do (if possible) a backup restore.