any way to "shrink" native db size except for rest

thebeerhunter

I'm not an expert at all with Navision. Have 3.70A.

I've noticed when setting up test copies of the db the actual file space taken up is much less than the size of my live db, even tho just restoring a backed up version of the live db.

Is there a way to "shrink" the native db somehow? The database size is 8 Gb but when I restore from backup the test db ends up almost half that.

Savatage

Is there any reason for not leaving it "as is" with the 8GB?

Are you running out of Hard Drive space?

File->Database->Information->Database tab

Your database size is 8GB - what's your database used?

Optimizing the tables can lower your Database Used.

---

I'm also wondering if you are creating a second company as a "test" database in the same database - doubling your size.. and when you create a new database, say on your own hard drive, of just one of the companies - it would appear as half.

Hope that made sence. :-s

thebeerhunter

We're using 77%. I read that you should expand before hitting 80% (is that true?) and I'm having to do this once every month or so.

Savatage

I try to keep mine between 75-85. If it uses too much room, when you try to optimize your large tables (ie/ G.L, Value Entries) it will not have enough space and you will have to expand.

I have found that if i optimize regualrly the tables that are >100000 in size that I don't have to expand every month.

kriki

Savatage wrote:

I try to keep mine between 75-85. If it uses too much room, when you try to optimize your large tables (ie/ G.L, Value Entries) it will not have enough space and you will have to expand.

I have found that if i optimize regualrly the tables that are >100000 in size that I don't have to expand every month.

But for performance it is better not to optimize the tables in which you write a lot (e.g. entry-tables, invoice headers/lines,...). This because after an optimize the system takes longer to put a new record in it. In general these tables stabalize optimiziation around 60%. This is for a native Navision-DB.
On SQL, on the contrary, it is usefull for space and speed to optimize.

Savatage

our server is good and the number of users is few.
Probably under 10 most of the time.
A slowdown is something we don't really need to deal with but our database can grow like a weed.

Optimizing is necessary for us.

7 more to 900..i feel old.

Marije_Brummel

You can shrink a database by making a backup and restoring in a new smaller database.