this blog is intended to help the NAV2009 administrators and not the developers. You can find several blogs about problems inside Navision, but only few with information about the installation and configuration of the NAV related servers and services. So I hope, you’ll find some helpful information in this blog.

 My first post will about the security delegation:
If you are the sysadmin of the SQL Server Instance for NAV you probably won’t have the time to add users inside NAV. But you also don’t want to give another person sysadmin rights to the SQL Server Instance.

In NAV2009 SP0 it was sufficient to give that person db_owner rights on the NAV database and securityadmin rights on an instance level.

With NAV2009 SP1 Microsoft changed that concept. You now have to give the following permissions:
- db_accessadmin on the master database
- db_securityadmin role on the NAV database
- db_owner on the NAV database
- securityadmin role on the SQL server

And then it should work.
But on some databases we received the following error message when adding a user to the database:

“The following SQL Server error or errors occured:
15151, “42000″, [Microsoft][ODBC SQL Server Driver][SQL Server] Cannot find the object ’sysprocesses’, because it does not exist or you do not have permission.

SQL:
GRANT SELECT ON sysprocesses TO [newUser]”

The sysprocesses is a view in the master database of the SQL instance. If you check, the server role “public” already has the select permissions. So the user adding actually worked, but as error messages are always disturbing we wanted to get rid of it. So now you have to give the user who should add new users to the database the following additional permissions:

GRANT SELECT ON master.dbo.sysprocesses
      TO [useradmin]     �
      WITH GRANT OPTION

GRANT VIEW SERVER STATE
     TO [useradmin]�
     WITH GRANT OPTION