Changes in Development between 3.7 and 4.0 Sp1

fduus

Hello,
tomorrow i have to do a small presentation about the Changes in Development between 3.7 and 4.0. I need just a little overview. I dont need any descriptions, just some keyowrds. The description an foils/charts for presentation i can work out for my self.

Thanks for helping me.

For now i got:
- The Navigation Pane / Menu Suite
- xml Ports

Are there any new data types or something else?

kine

4.00 
	XMLPort
	MenuSuite
	
4.00SP1
	FINDSET,FINDFIRST,FINDLAST
	Record Set (Database - Alter)
	TIMEOUT (C/AL command and new Option in Database - Alter)
	ROWLOCK (Database - Alter)
	SQLIndex property on keys
	Clustered property on keys

fduus

kine wrote:

4.00 
	XMLPort
	MenuSuite
	
4.00SP1
	FINDSET,FINDFIRST,FINDLAST
	Record Set (Database - Alter)
	TIMEOUT (C/AL command and new Option in Database - Alter)
	ROWLOCK (Database - Alter)
	SQLIndex property on keys
	Clustered property on keys

Need some description for SQLIndex prperty on keys / Clustered....

kine

Through SQLIndex you can define how the key will be represented as index on MS SQL. For each Navision key is MS SQL Index created (if you have MaintainSQLIndex Yes) - but because SQL need indexes with good selectivity to work fast, you can change for example field positions in the index to have better index (move fields with good selectivity to first positions etc.). See on-line help for that property. (MS SQL do not need the indexes for sorting, it means the fields can be in different order etc.). This is for performance optimalization when using MS SQL. See Performance troubleshooting guide for more details about tha.

Clustered - clustered indexes are much better for performance on MS SQL, they are used in another way than common indexes. This property you can use when you want to select another index on MS SQL as clustered (something like Primary Key in Navision but... :-))

fduus

Thanks for your help.

I think i´ve got all informations i need.

thaug

Remember with 4.0 that a bug exists with the PK's not being set as clustered. MS offers a hotfix with a T-SQL script to change the PK's to clustered, and I believe that this should be solved in 4.0 SP2.

Phenno

there is a new data type: BigText