We will look at the first component in a Microsoft Dynamics AX installation; database. The following screenshot shows the option in Dynamics AX 2009 setup that achieves this. This option will create a database in Microsoft SQL Server with the necessary stored procedures. If you intend to use Oracle database, you will have to create the database manually. Do take time to ensure you have the required software installed.
You may run this setup on any computer that has access to the Database server. The user account that you use to execute this must be a member of the dbcreator role on the target SQL Server instance. If you are using the administrator account, your account will most likely be a member of the sysadmin role which has the rights of all the roles combined. The following figure shows the property page of a SQL Server login.
Before you begin
Before you jump into the installation of this component, there one thing I would like you to take note. The installation creates a database without asking you for the location of your data file and log file. It is important that these files are in separate and preferably dedicated physical drive. I suggest that you configure the default file locations in accordance your database server storage plan. This specifies the data and log files locations for databases created subsequently.
Dynamics AX Setup - Database
The Database installation is fairly simple. You just have to specify the Microsoft SQL Server instance you would like to create the database on and the name you would like for your new database. The following screenshot illustrates the information collected for this setup.
Upon completion, you will have a new database with two user stored procedures; CREATESERVERSESSIONS and CREATEUSERSESSIONS. The rest of the objects will be created in subsequent steps of the installation.
Database Access
This database is intended to be accessed by appropriate AOS instances. The account that starts the AOS instances requires certain authority to work correctly. The account must be assigned the db_datareader, db_datawriter and db_ddladmin database roles as shown in the figure below. The first two roles allows AOS to read and write data on the database whereas the final role allows the AOS to create, change and remove objects in the database. DDL in the role name refers to data definition language.
Besides these database roles, the AOS account also need execute permission on the two procedures; CREATESERVERSESSIONS and CREATEUSERSESSIONS. The following figure shows the permission configuration for stored procedure.
Conclusion
This step of the setup process takes little time. There are just a few minor things you should take note to ease the installation of other components as well as administration the system in the long run.
0 comment :