I would like to know what differences in database size can be
expected for a v2.6 database running on the Navision database
engine compared to the SQL engine.
The total size of a Navision database using SQL is larger than C/Side, by approximately 50 percent. For example, I backed up a database that had a SQL dataset 350mb in size, and it restored into a C/Side database of 200mb.
SQL Server gains some of its performance by having a certain amount of "empty" pages inside the dataset. You do have some control over the increments by which a SQL database expands. But once running, if you look at the database information inside Navision, a SQL database will continually run at about 85% full. When it reaches a certain threshold, it will automatically expand.
Ron
<BLOCKQUOTE><font size="1" face="Verdana, Arial">quote:</font><HR>Originally posted by dwest: I would like to know what differences in database size can be
expected for a v2.6 database running on the Navision database
engine compared to the SQL engine.
Comments
SQL Server gains some of its performance by having a certain amount of "empty" pages inside the dataset. You do have some control over the increments by which a SQL database expands. But once running, if you look at the database information inside Navision, a SQL database will continually run at about 85% full. When it reaches a certain threshold, it will automatically expand.
Ron
<BLOCKQUOTE><font size="1" face="Verdana, Arial">quote:</font><HR>Originally posted by dwest:
I would like to know what differences in database size can be
expected for a v2.6 database running on the Navision database
engine compared to the SQL engine.
Can anybody help?
TIA
David <HR></BLOCKQUOTE>
Ron Saritzky
email ron@scs-accounting.com