Does anyone know if it's ok to run a 4.0SP2 client on a 2.60 SQL-database?
I want to get the latest finsql.exe-updates to run the old 2.60-database as fast as possible.
Will work but you have to change all functions find('-'),... with the new functions findfirst, findlast and findset if you want a really better way on SQL Server!
But don't forget C/AL in 2.60 was not really optimize for SQL Server. [-o<
Will work but you have to change all functions find('-'),... with the new functions findfirst, findlast and findset if you want a really better way on SQL Server!
But don't forget C/AL in 2.60 was not really optimize for SQL Server. [-o<
No no no no no.... you don't HAVE to do anything. FIND('-') still works. The only reason you should look into rewriting any code is if you are having actual performance problems. If your system is running fine you should not even think about doing this.
A (quite) fast way to get a lot of performance is not to control all the code in the 2.60 DB but do some checking of the indexes/SIFT fields in Navision. A lot of those don't have to be maintained in SQL. Some indexes can be reworked (eg. an index with "Document Type","Document No." in SQL is better to have only 1 field in the index:"Document No.").
And the funny/beautifull thing is:you don't have to rewrite a single line of code, only update the properties of the indexes.
Regards,Alain Krikilion No PM,please use the forum. || May the <SOLVED>-attribute be in your title!
Comments
But don't forget C/AL in 2.60 was not really optimize for SQL Server. [-o<
RIS Plus, LLC
It's a hard work to optimize C/AL of 2.60 to obtain good speed!
Good luck
It was the updated finsql.exe I was after in the first place.
To re-write all FIND will have to wait...
Best regards,
Torbjörn
And the funny/beautifull thing is:you don't have to rewrite a single line of code, only update the properties of the indexes.
No PM,please use the forum. || May the <SOLVED>-attribute be in your title!