Native DB vs. SQL-DB

rkadenbach
rkadenbach Member Posts: 15
edited 2002-09-17 in Navision Financials
I am interested in information about the differences between Navision (in my case 2.60D) using the native DB and an SQL-based DB.

- Are there differences in the required hw?
- What about performance and stability?
- Regarding the same content, are there differences in the size of the DB?

Thanks and greetings from Germany

Ronny

Comments

  • Christian_Buehl
    Christian_Buehl Member Posts: 145
    Hi Ronny,
    if you are not suicidal use the native database.
    The native database is fast very reliable and very easy to handle. You can copy the database by filesystem and in 3 Years of usage I had not any problem (even with some hardware failures). It still works fast and well on a Pentium 400 machine with 128 MB of RAM.
    If I will run the same with SQL-Server would consider only the newest hardware (2 GHZ, U-160 Harddisks, 1 GB RAM) for gathering the same performance.
    I estimate also about 5 to 10 hours extra work each week for maintenance of the SQL-server. (Additional you will need some more time for trainings)
    Greetings
    Christian
  • rkadenbach
    rkadenbach Member Posts: 15
    The Problem is that we use NF as billing-engine. It's planned as a warm billing-system, but we're using it as a cold billing-system for the next 6 months.
    This results in that we have to modify about 15 millions of records in a table containing about 50 million records. And that each month again.
    Wouldn't it be better (faster/more stable and so on .. see my first posting) to switch to an sql-system? The newest HW is already in use here(even more than you suggested), so it wouldn't be a problem.
    In a short form:
    If I had 2 machines with the same HW(high-end <img border="0" title="" alt="[Wink]" src="images/smiles/icon_wink.gif" /> and I were running on the one machine the native DB and on the other an sql-based DB, which one would be the faster one and, as the most important, the more stable?

    Greetz,

    Ronny
  • Christian_Buehl
    Christian_Buehl Member Posts: 145
    IMHO it is not really a problem to write an little dataport for such an import/export.
    If you plan to access the database from other applications via ODBC it will probably work easier with the SQL-Server. But don't forget all the maintainance and update-stuff you need to do for the SQL-Server. If you are already an expirenced Administrator for SQL-Server than have fun with this. But if not, you can definitely sleep much better with the native database.

Categories