Navision native db - SQL Server Option

WaldoWaldo Member Posts: 3,412
edited 2010-03-03 in Navision Attain
I know that SQL Server supports record level locking, Navision native db does not (table locking). Is it so that when we use the SQL Server option, the tablelocks will decrease, or will it be just te same as in the Navision Native db??

Is there some kind of paper the describes the differences (advantages and disadvantages) between SQL Server and Native db?

Eric Wauters
MVP - Microsoft Dynamics NAV
My blog

Comments

  • rictsangrictsang Member Posts: 8
    you can find the document from NSC. They have explained the difference between Navision native database and SQL database, like security, database administration, advantage and disadvantage.

    Richard
  • andy76andy76 Member Posts: 616
    Hi,

    What do you mean by NSC?
    Where can I find this info?
    Is there some link?

    Thank you
  • WaldoWaldo Member Posts: 3,412
    that's kind of a late reply :mrgreen:

    NSC = Navision SOlutions Center

    I don't think there is a document available you're looking for. What exactly is your problem?

    Eric Wauters
    MVP - Microsoft Dynamics NAV
    My blog
  • David_SingletonDavid_Singleton Member Posts: 5,479
    Waldo wrote:
    I know that SQL Server supports record level locking, Navision native db does not (table locking). Is it so that when we use the SQL Server option, the tablelocks will decrease, or will it be just te same as in the Navision Native db??

    Is there some kind of paper the describes the differences (advantages and disadvantages) between SQL Server and Native db?


    :shock: :shock: :shock:

    You can read waldo's blog for lots of great information about this! :mrgreen::mrgreen::mrgreen:
    David Singleton
  • andy76andy76 Member Posts: 616
    I am preparing a brief presentation power point to explain the differences and advantages of SQL Server to convince new project to start directly in SQL or to migrate to SQL.

    Thank you
  • WaldoWaldo Member Posts: 3,412
    Waldo wrote:
    I know that SQL Server supports record level locking, Navision native db does not (table locking). Is it so that when we use the SQL Server option, the tablelocks will decrease, or will it be just te same as in the Navision Native db??

    Is there some kind of paper the describes the differences (advantages and disadvantages) between SQL Server and Native db?


    :shock: :shock: :shock:

    You can read waldo's blog for lots of great information about this! :mrgreen::mrgreen::mrgreen:

    lol, that's true :-)

    Eric Wauters
    MVP - Microsoft Dynamics NAV
    My blog
  • David_SingletonDavid_Singleton Member Posts: 5,479
    Waldo wrote:
    Waldo wrote:
    I know that SQL Server supports record level locking, Navision native db does not (table locking). Is it so that when we use the SQL Server option, the tablelocks will decrease, or will it be just te same as in the Navision Native db??

    Is there some kind of paper the describes the differences (advantages and disadvantages) between SQL Server and Native db?


    :shock: :shock: :shock:

    You can read waldo's blog for lots of great information about this! :mrgreen::mrgreen::mrgreen:

    lol, that's true :-)


    I added the mr green after I saw the date on the original post. Blast from the past or what.
    David Singleton
  • David_SingletonDavid_Singleton Member Posts: 5,479
    andy76 wrote:
    I am preparing a brief presentation power point to explain the differences and advantages of SQL Server to convince new project to start directly in SQL or to migrate to SQL.

    Thank you

    Here is an article I wrote many years back to do the exact same thing:

    C/SIDE database vs SQL

    back then it was a tough decision as to which to use. But for at least 3 years now the advantages of SQL far outweigh Native.
    David Singleton
  • David_SingletonDavid_Singleton Member Posts: 5,479
    andy76 wrote:
    I am preparing a brief presentation power point to explain the differences and advantages of SQL Server to convince new project to start directly in SQL or to migrate to SQL.

    Thank you

    Here is an article I wrote many years back to do the exact same thing:

    C/SIDE database vs SQL

    back then it was a tough decision as to which to use. But for at least 3 years now the advantages of SQL far outweigh Native.

    Oh and Andy you are free to use that article in your power point, so long as you credit where you got it from. :wink:
    David Singleton
  • andy76andy76 Member Posts: 616
    I read a lot of time ago that there are restrictions about database native regarding dimension and number of users that there are limits.
    Where can I find these detailed informations about db dimension, RAM exploitation, CPU and so on?

    Thank you very much
  • WaldoWaldo Member Posts: 3,412
    If I'm not mistaken, you can find a lot in the Application Developmer's Guide (ADG) on the product CD.
    You can explore the partnersource as well for hardware-stuff.
    But again, a lot you can find on the forums. It's actually quite simple: native only supports 1 CPU and 1Gb RAM. That's it. Not really scalable for that matter.

    Eric Wauters
    MVP - Microsoft Dynamics NAV
    My blog
  • David_SingletonDavid_Singleton Member Posts: 5,479
    andy76 wrote:
    I read a lot of time ago that there are restrictions about database native regarding dimension and number of users that there are limits.
    Where can I find these detailed informations about db dimension, RAM exploitation, CPU and so on?

    Thank you very much

    It's quite simple, Microsoft have made a decision not to support two database servers, and obviously they are not going to drop SQL. Thus Microsoft have done no development at all on the Navision Native database, and even though at its peak, the Native database was one of the most technically advanced Databases out there, that was 15 years ago, and in reality nothing has changed since the DOS version. currently the only issues with Navision on SQL, are 1/ the added cost, 2/ some additional maintenance, 3/ the application is still in soe places optimized for the native database not SQL.
    David Singleton
Sign In or Register to comment.