Cannot Expand Database

Iris2006

Hi,

I am using Navision 3.7

I am getting an error when trying to expand my current database by just 16kb

The error say the following: Your server returned the following message - not enough disk space".

I have 16GB of diskspace left. How can this be?

Also not sure if this is worth mentioning but a FAT32 file systems is being used.

Please can you give me some light on this error and explain how to resolve

Luc_VanDyck

With the FAT32 filesystem, you cannot create files > 4 GB. See also http://www.mibuso.com/forum/viewtopic.php?t=7721 .

So you should split up your database in separate files of 4 GB each.

And remember: Search is your friend: http://www.mibuso.com/forum/search.php

Iris2006

Thanks for the help

Just one small problem, I am fairly new to Navision and not too how I go about splittung the database and what the repurcussions would be.

Your help would be greatly appreciated

Savatage

any particular reason why you're using FAT32?

Iris2006

Its one of our clients, not too sure as to why they are using it :?

Savatage

Fat32 vs NTFS
http://thundercloud.net/information-ave ... -vs-fat32/

1) If you have a hard drive over 40 gig in size, be certain to choose the option NTFS.

2)Your hard drive may not appear to be as big as it really is when using FAT32; so when given a choice, use NTFS.

3)NTFS is more reliable and secure!

4)It is best to format your hard drive and choose the NTFS file system, instead of converting an existing drive from NTFS without a format.

5)If your hard drive is larger then 32 GB, use NTFS for best performance.

What is Microsoft's recommendation on this? NTFS is the recommended file system for computers running the Microsoft Windows XP and Windows .NET Server operating systems. NTFS offers many end-user benefits related to functionality, security, stability, availability, reliability, and performance. NTFS, which was originally introduced with Microsoft Windows NT® 3.1, has always provided advanced file system features such as security, transacted operations, large volumes, and better performance on large volumes. Such capabilities are not available on either FAT16 or FAT32

I just think it would be easier & better for them to switch rather than going thru a database split which you are going to need more drives anyway.

Luc_VanDyck

Iris2006 wrote:

Just one small problem, I am fairly new to Navision and not too how I go about splittung the database and what the repurcussions would be.

Did I already mention you can search this forum? Hint: try "split and database" as search keywords, and you find, among others, this topic: How To Split A Database

themave

you can also find out how to do it, buy using the Navision help, you will find this:

You can expand your Navision database by creating extra database files.

To Create a New Database File:
Click File, Database, Expand and the Expand Database window appears.

Click Advanced and the Expand Database (Advanced) window appears.

The "proper" name of the database is written in the Database Name field. This is the name that will be referred to in the future from other places in the program. If you need to use the name of the database to open it or to make a backup of it, use this name and ignore the fact that the database actually consists of more than one file.

Each new database file must be set up on its own line.

In the File Name field, enter the name (with the full path).

If the database name is My db.fdb, for example, and it is located in c:\fin\, you can call the new database file My db part2.fdb and put it on another drive: d:\fin\.

A third database file could be called My db part3.fdb and be located on yet another drive.

In the New Size(KB) field, enter the size of the database file.

At the bottom of the window, you can see how the entire database grows as you add kilobytes with each file you create.

Click OK to save the information. You can continue working in the database.

In order to expand your database, you must have adequate space available. (You can see the space you have available in the Licensed Size(KB) field.)

If you do not have permission to expand the database, an error message will appear when you try to expand it.

There is no advantage to be gained by expanding your database to the maximum size because once space has been allocated to the database, it cannot be reclaimed again and you can't use it for anything else on your computer.

Savatage

Here's an old white paper I have

Scenarios:
1. Creating a new database and restoring data.
2. Expanding existing parts of a database
3. Expanding using existing and newly created parts of a database
4. Fixing a 'non optimized' database.

1. Creating a new database and restoring data

If you create a new database that is spread over several disks, you must close and reopen the database before restoring data. This will recover the 'List of Free Blocks' and the restored data will be equally spread over all disks, thus securing the optimal performance.

To spread the data equally over the new database, you must follow these steps:

Create a new database and expand it with database parts of the same size
Close and reopen the database (rebuild 'List of Free Blocks')
Restore the backup.

2. Expanding existing parts of a database

If you expand existing parts of a database that is spread over several disks, you must close and reopen the database before using it again. This will update the 'List of Free Blocks' and secure the optimal performance.

Expand all database parts with the same size
Close and reopen the database (rebuild 'List of Free Blocks').

3. Expanding using existing and newly created parts of a database

If you expand a database by one or more new database parts on new disk(s), you should follow the correct procedure (D). If you haven't done so, you must at least close and reopen the database so that Navision recognizes the new disk(s) and starts using it . If you don't close/reopen, it will continue to use the old 'List of Free Blocks' and will take some time before the list wraps around and starts using the new disk(s). The database is now 'non optimized', because data is not spread equally over the disks. Procedure (D) tells you how to fully optimize the database.

4. Fixing a 'non optimized' database

To spread the data equally over all parts of a database, follow these steps:

a. Make a Navision backup
b. Delete the database
c. Create a new database with the required parts of the old database
d. Close and reopen the database (rebuild 'List of Free Blocks')
e. Restore the backup.

This procedure is the optimal way of adding a new database part, but it is also the most time consuming.

Iris2006

Thanks for the help guys