When you install Microsoft SQL Server as the relational database, select Binary for Sort Order on the server. If you do not select Binary or Case-sensitive for Sort Order, even when you select the Match case check box in the Find dialog box displayed in the Destination window, the Match case setting is not enabled. Also, the count-clients facility of Inventory Viewer and the output range setting facility of the CSV output utility will not distinguish between uppercase letters and lowercase letters.

After you have created the database for JP1/Software Distribution, do not change the database sorting order. If you change the database sorting order and any discrepancy with the sorting order of the relational database server occurs, the system is not guaranteed to run correctly.

To use a relational database, you must set up the network protocol in both the relational database server and the clients. This subsection describes the settings for each relational database program.

• Settings in the relational database server
  Select the protocols that the relational database server can use to connect to the managing server and Remote Installation Manager. Normally, you would use TCP/IP Sockets or Named Pipes.
  
• Settings in the relational database client
  In the relational database client, set the same protocols you selected in the server.
  

For details about how to set the network protocols, see the Microsoft SQL Server documentation.

Be sure to copy down the protocol and server names that you set here, because you will need them when you create the relational database.

You do not have to set the items, because Microsoft SQL Server 2012, Microsoft SQL Server 2008, Microsoft SQL Server 2005, Microsoft SQL Server 2000, and Microsoft SQL Server 7.0 have a function that tunes the operating environment automatically. However, you can change the database server settings as necessary.

To change the setting for the number of locks, use Transact-SQL. To change the settings for the number of connected users and the maximum memory size that can be used, go to the Connections and Memory pages of the SQL Server Properties dialog box. You can also allocate a fixed memory size.

Memory allocation for Microsoft SQL Server is important in order to use JP1/Software Distribution efficiently to perform remote installation. The following explains how to estimate the memory allocation in Microsoft SQL Server.

(a) Data cache

The data cache consists of the index page and data page of each table. The following shows the calculations for estimating the memory allocation for the index page and data page of a frequently-accessed table. It is recommended that you allocate memory for 100% of the index page and at least 20% of the data page. If there is sufficient memory, allocate memory for 100% of the data page. The number of packages includes the number of already-distributed packages and the number of packages to be distributed.

Index page

Number of managed clients x number of packages x 0.0005 (megabytes)

Data page

Number of managed clients x number of packages x 0.0045 (megabytes)

(b) Procedure cache

The procedure cache consists of Microsoft SQL Server's execution plans, etc. When you use JP1/Software Distribution, allocate about five megabytes of memory to the procedure cache.

Microsoft SQL Server 2012, Microsoft SQL Server 2008, Microsoft SQL Server 2005, Microsoft SQL Server 2000, and Microsoft SQL Server 7.0 adjust the memory allocations dynamically in order to optimize their performance. Normally, the system administrator does not need to set memory allocations. However, the system administrator should set maximum and minimum values, taking into account the overhead due to automatic adjustment of memory allocations.

Minimum value

At least 16 megabytes

Maximum value

Total amount of memory - (amount of memory used by the operating system + amount of memory used by JP1/Software Distribution^# + amount of memory used by other applications + 5 megabytes)

#: See 5.3.2 Memory requirements in the Description and Planning Guide.

Select SQL Server and Windows as the authentication mode. You can set the authentication mode in Security on the Security page of the SQL Server Properties dialog box.

If the ID key for relational database access that you set in JP1/Software Distribution Manager is not the system administrator ID of Microsoft SQL Server, you must set access permissions for each table in the relational database. The required access permissions are SELECT, INSERT, UPDATE, and DELETE.

To set access permissions:

For Microsoft SQL Server 2012, Microsoft SQL Server 2008 and Microsoft SQL Server 2005

If you create new ID:

1. In the Object Explorer of Microsoft SQL Server Management Studio, select database name, Security, and then Logins. Right-click on Logins, and select New Login.
2. In the Login - New dialog box, set a login name and authentication:
   From the Select a page pane of the Login - New dialog box, select the General page, and set a login name and authentication. If you select SQL Server authentication, you need to set Password and Confirm password. If you select the check box User must change password at next login, do the step 5. below to change the password.
   
3. In the Login - New dialog box, specify the users mapped to the login and the database role membership:
   From the Select a page pane of the Login - New dialog box, select the User Mapping page.
   For Users mapped to this login, select the created database name. For Database role membership for database name, select the following check boxes:
   
   • db_datareader
   • db_datawriter
   • db_ddladmin
4. Click OK in the Login - New dialog box.
5. Log on to the server with the created new ID. If you set User must change password at next login in the step 2. , the Change Password dialog box appears. In the Change Password dialog box, change the password.

If you use the existing ID:

1. In the Object Explorer of Microsoft SQL Server Management Studio, select
   database name, Security, and then Logins. Select ID for which you will be setting access permissions. Right-click on the selected ID and select Properties.
   
2. In the Login Properties - (selected ID name) dialog box, and specify
   the users mapped to the login and the database role membership. From the Select a page pane of the Login Properties - (selected ID name) dialog box, select the User Mapping. For Users mapped to this login, select the check box for the created database name. For Database role membership for database name, select the following check boxes:
   - db_datareader
   - db_datawriter
   - db_ddladmin
   
3. Click OK in the Login Properties - (selected ID name) dialog box.

For Microsoft SQL Server 2000 and Microsoft SQL Server 7.0

If you create new ID:

1. In SQL Server Enterprise Manager, select database name, Security and then
   Logins. Right-click on Logins, and select New Login.
   
2. In the SQL Server Login Properties - New Login dialog box,, set a login name and authentication:
   On the General page of the SQL Server Login Properties - New Login dialog box, set a login name and authentication. If you select SQL Server authentication, you need to set Password.
   
3. In the SQL Server Login Properties - New Login dialog box, specify database that can be accessed by the login, and the database roles:
   Select the Database Access page in the SQL Server Login Properties - New Login dialog box.
   For Specify which databases can be accessed by this login, select the check box for the created database name. For Database roles for database name, select the following check boxes:
   - db_datareader
   - db_datawriter
   - db_ddladmin
   
4. Click OK in the SQL Server Login Properties - New Login dialog box. If you set Password in the step 2. , the Confirm Password dialog box appears. In the dialog box, enter the password again.

If you use the existing ID:

1. In SQL Server Enterprise Manager, select database name, Security and then
   Logins. Select ID for which you will be setting access permissions. Right-click on the selected ID and select Properties.
   
2. In the SQL Server Login Properties - (selected ID name) dialog box, specify database that can be accessed by this login and the database roles:
   Select the Database Access page in the SQL Server Login Properties - (selected ID name) dialog box.
   For Specify which databases can be accessed by this login, select the check box for the created database name. For Database roles for database name, select the following check boxes:
   - db_datareader
   - db_datawriter
   - db_ddladmin
   
3. Click OK in the SQL Server Login Properties - (selected ID name) dialog box.

Microsoft SQL Server collects a history of accesses for relational database updating in a transaction log. Although JP1/Software Distribution Manager allocates a transaction log when the relational database is created, users cannot gain access to the relational database if the transaction log becomes full. If you set the file size of the transaction log to increase automatically, the log will reach a maximum size of 2 TB, which will decrease the response speed of the disk due to decreased disk availability.

We recommend you that you set up the transaction log so that it is deleted automatically.

For Microsoft SQL Server 2012, Microsoft SQL Server 2008 and Microsoft SQL Server 2005

1. Start Management Studio.
2. Select the target database, and then open the Database Properties dialog box.
3. Choose the Options menu.
4. From Recovery model in the left-hand frame of the dialog box, select Simple.

For Microsoft SQL Server 2000

1. Start Enterprise Manager.
2. Select the target database and then open the Properties dialog box.
3. On the Options page, from Model, select Simple.

For Microsoft SQL Server 7.0

1. In the SQL Enterprise Manager window, right-click on the target database to open a pop-up menu, and then choose Properties.
2. In the XXXXX Properties dialog box (XXXXX is the database name), on the Options page, select the Truncate log on checkpoint check box.

If the transaction log file becomes full while the Truncate log on checkpoint check box is not selected, JP1/Software Distribution Manager outputs a message to RDBSRV.LOG that indicates no object area can be allocated in the segment. If this message is output, use the following procedure to discard the transaction log:

For Microsoft SQL Server 2012, Microsoft SQL Server 2008 and Microsoft SQL Server 2005

In Management Studio, from the menu that is displayed by right-clicking the database, choose Tasks, and then Back Up to display the Back Up Database dialog box. From the General tab of this dialog box, make a backup of the transaction log information. As much transaction log information as is backed up will be discarded.

For Microsoft SQL Server 2000

Use the Backup Database menu of Enterprise Manager to make a backup of the transaction log. The data you back up will be deleted from the log.

For Microsoft SQL Server 7.0

Use the Truncate Log menu of Enterprise Manager to truncate the transaction log. Alternatively, use Query Analyzer to specify a DUMP statement (DUMP TRANSACTION database-name WITH NO_LOG) and delete the transaction log.