In order to install DotNetNuke you will need an empty
Microsoft SQL Server 2000/2005/2008 database. Interestingly
Regional Settings of your
Control Panel could affect the result of DotNetNuke Installation. Not directly but, in a complicated way.
Note to Turkish/Azeri/Arabic Community Users of DotNetNuke:
For better results ensure that your Server Collation configured correctly.
Connect to
Microsoft SQL Server Management Studio using
Windows Authentication.
Right click to SQL Server Instance from
Object Explorer and select
Properties.
From
General tab check
Server Collation and ensure that it is
SQL_Latin1_General_CP1_CI_AS.
Note: Turkish users will have issues with
Turkish_CI_AS as server collation. It is strongly recommended to configure
SQL Server Environment for Turkish Community to have
Latin1_General_CI_AS as server collation. If you use different collations for server and database, you will most likely have issues like
collation conflicts.
Let's get back to main topic of creating database.
Expand Databases tab from Object Explorer.
Right click to
Databases tab and select
New Database from menu.
Type your database name (e.g
odnn09) to
Database Name field and click
OK button from bottom section of
New Database window.
Now you need to create user under
Security > Logins tab and assign permissions to this user.
Expand
Security tab from
Object Explorer.
Right click to
Logins and select
New Login.
New Login Wizard (Login Properties Window - [Login - New])
Choose a unique
login name (e.g
odnndbuser) and type it to
Login Name field.
Default Authentication method is
Windows Authentication. Switch this to
SQL Server Authentication. This will enable sub settings of
SQL Server Authentication.
Type a complex password and confirm it.
Uncheck Enforce Password Policy checkbox. This will also uncheck Enforce password expiration and User must change password at next login checkboxes.
Select your database from Default database list. (e.g odnn09).
Do not click OK button yet.
Navigate to User Mapping.
Select your database under Users mapped to this login and check db_owner permission from Database role membership for section.
Now you can click OK button.
If everything in place, you should have a database configured under Databases section and a user configured under Logins. (see the example below)
