Archive for August, 2013

SQL Server in Windows Authentication Mode

Administrators can login to SQL Server either in Windows Authentication Mode or SQL server authentication mode. In the Windows Authentication mode, whenever you login to SQL server, you need not to provide the credentials; SQL Server uses your Windows credentials.

1)       Open SQL Server Management Studio, connect to the database server using SQL Server Authentication.

2)       Click Server > Security, and then right-click Logins and select New Login.

3)       Enter the login name in Login Name box [domainName/Username].

4)       Select the Windows Authentication.

5)       Leave the Default Database to Master

6)       In the Select a page pane, click Server Roles, select the sysadmin check box, and then click OK.

7)        Disconnect the Object Explorer and again Connect in Windows Authentication mode.

In the following procedure, [database_name] represents the name of the windows Authenticated DB.

8)       Click Server > Databases > Right Click on Databases and click New Database.

9)       Enter the database name of your choice for example: [database_name].

10)   (SQL Server 2005 Only) Ensure that Use Full-Text Indexing is deselected.

11)   In the Database Data Initial Size MB box, enter the appropriate value:

•      For small development or small production systems, specify 200 MB.

12)   In the Database DataAutogrowth box, enter 50%.

13)   In the Database Log Initial Size box, enter the appropriate value:

•      For small development or small production systems, specify 20 MB.

14)   In the Database LogAutogrowth box, enter 50%.

15)   Click OK to create the database.

16)   Click Server > Databases > [database_name] > Security, and then right-click Schemas and select New Schema.

17)   In the Schema Name box, type an appropriate schema name, example: [schema_Name], and click OK.

18)    Change the default owner to ‘sa’. The detailed steps are listed below:

        18.1 In SQL Management Studio menu, click New Query.

        18.2 In the query Panel, type the following command:

         Use [database_name] EXEC sp_changedbowner 'sa'

        18.3 Click Execute. A success response is displayed in the messages panel.

19)   Click Server > Databases > [database_name] > Security, and then right-click Users and select New User.

20)   Select user Type “Windows User” from the drop down menu.

21)   In the New User dialog box, type the login name and user name as [domainName/UserName] as created through steps 1-7.

22)   Set the default schema to schema created as in step 16-17.

23)    (SQL Server 2008 R2) In the Schemas Owned by this User area, select the schema as created in step 16-17.

24)   Click Server > Databases > [database_name] > Security, and then right-click schema  [created in step 16-17] and select properties and  select permissions

a)       Click search button in Users or Roles and type [database_username] and click OK.

b)       In the Explicit tab grant  the following permissions:

   1. Alter

  2. Insert

 3.  Reference

 4.  Select

 5.  Update

6.  Delete

c)       Click OK.

 25)   Right Click Server > Databases > [database_name] and select properties then select permissions tab

a)       Select Explicit tab

b)       Grant the following  permissions:

1. Connect

2. Create Table

3. Create View

c)       Click Ok.

Associate the LiveCycle user with the database

After you create the LiveCycle user, associate it with the LiveCycle database.

26)   Click Security > Logins, and then right-click [domainName/UserName] and select Properties.

27)   In Login Properties, on the General page, set the user’s default database to [database_name].

28)   Select the User Mapping page and, in the Users Mapped to This Login section, verify that [database_name] is selected, User is set to [domainName/UserName], and Default Schema is set to [schemaName created in step 16-17].

29)   Ensure that [database_name] is selected in the Users Mapped to This Login table, and ensure that public is selected in the Database Role Membership for [database_name] table and then click OK.

Set the isolation level for the LiveCycle database

 LiveCycle requires a specific isolation level to manage deadlocking when long-running transactions occur at the same time as numerous shorter reads.

Important: You must set the isolation level for MS SQL Server to avoid deadlocking issues.

1)        Click Databases and then right-click [database_name] and select New Query.

 Note: [database_name] represents the name you specified when you created your database.

 2)        In the Query panel, type the following text:


3)       Click Execute. A response is displayed in the messages panel.

 Note: In order to deploy the LC when DB is in Windows Authentication Mode, Application Server and DataBase user must be created under same user (DomainName/Username). If Application Server and DataBase do not fall under same user, then create the common user on both the Systems which are having DB and App Servers.

VN:F [1.9.22_1171]
Was this helpful? Please rate the content.
Rating: 0.0/10 (0 votes cast)