SQL Server Programming

WaldoWaldo Member Posts: 3,412
edited 2003-08-28 in Navision Attain
I know that when you migrated to SQL Server, the users should have less problems with tablelocks. Now, I also know that the developer should develop in another way, when working on a SQL SERVER. Even, when migrated, I suppose the developer should do some changes on the existing code.

Is there a summary of what the developer should change on the existing code, and how the developer should develop on the SQL Server implementation?

Eric Wauters
MVP - Microsoft Dynamics NAV
My blog

Comments

  • SbhatSbhat Member Posts: 301
    Hi Waldo,

    If you go to Microsoft partners network, you will find a document that tells you programming changes in SQL environment. Not many changes but some locking functionalities. Please check the partners network for more details.

    Thanks
    Best regards
    Suresh.
  • nunomaianunomaia Member Posts: 1,153
    In Navision Database there is only table locking, in the SQL SERVER is row locking. Row locking improves performance, to understand I recomend to read the apllication desinger's guide, that explain's very well

    I recomend too to use FIND('-') instead of FIND('+') because in SQL server FIND('+') decreases performance, it returns all the records, it's better to use ASCENDING(FALSE) andFIND('-').
    Nuno Maia

    Freelance Dynamics AX
    Blog : http://axnmaia.wordpress.com/
  • Luc_VanDyckLuc_VanDyck Member, Moderator, Administrator Posts: 3,633
    Have a look at the upgrade manual w1w1upgr.pdf which is located on the product CD in the folder Upgtk\Doc. There is a chapter titled "Migrating to the Microsoft SQL Server Option for Navision 3.70" what describes the changes needed.
    No support using PM or e-mail - Please use this forum. BC TechDays 2024: 13 & 14 June 2024, Antwerp (Belgium)
Sign In or Register to comment.