You cannot set a non-nullable integer to 0 if SQL Server has a -1 default value for it. EF detects this as a "default" value for a non-nullable int and ignores sending it in the SQL statement.

In our organization we want to make the data from some SQL Server databases available on the intranet for people to view. I have already set up all data access to be done through stored procedures ...