Setting The Service Owner For Sql Server; Installation Of Microsoft Sql Server Software; Installation Of Sql Server On The Nas 8000; Installation Of Sql Server On A Windows Server - HP StorageWorks 8000 - NAS User Manual

following: -T1807. The -T1807 specifies the setting of trace flag 1807, which is the trace flag that enables
SQL Server to utilize "non-local" storage for database data files. Click on OK.
It is possible to set trace flag 1807 through the Query Analyzer or through the use of ISQL or ISQLW rather
than altering the startup parameters of SQL Server. Execute the Query Analyzer or ISQL/ISQLW and
execute the following SQL statement:
DBCC TRACEON (1807)
This statement must be executed at least once each time SQL Server is started and database(s) are created
utilizing the NAS 8000 for data/log file storage. If the startup parameters are not modified as above, then
the trace flag will need to be set each time that SQL Server is restarted if new databases are to be created.
The preferred method is to alter the startup parameters to set the trace flag automatically.

setting the service owner for SQL Server

The next task that should be completed before a database is created (or moved) on the NAS 8000 is to set
the owner for all SQL Server database services. This task only needs to be completed if the NAS 8000 is
in User/Domain level security, although it will not cause any undesirable side effects if the NAS 8000 is in
Share level security. Open the SQL Server Enterprise Manager utility and drill down through the navigation
tree until the SQL server to be managed has been selected. Select "Tools" from the menu, and then select
SQL Server Configuration Properties. Under the 'Security' tab, change the Startup Service Account by
clicking on the "This Account" radio button. Fill in the User ID and Password fields with a valid user id and
password from the Domain that the NAS 8000 has joined. It is possible to specify the Domain in the User
ID field by using the syntax: DOMAIN\UserID. Once this step has been completed, the SQL Server service
will execute as a member of the Domain. When the database data/log files are created on the NAS
8000, the SQL Server service will appear as a valid member of the Domain so there will not be a security
failure from the PDC.

installation of Microsoft SQL Server software

installation of SQL Server on the NAS 8000

It is not supported to install the SQL Server executables onto the NAS 8000 storage. SQL 7.0 and SQL
2000 will refuse to install if an attempt is made to place SQL Server on a 'non-local' hard drive. Neither
the program files, nor the data files for the SQL Server system databases, (master, msdb, model and
tempdb) can be placed on the NAS 8000.

installation of SQL Server on a Windows Server

It is the only supported installation configuration to install the SQL Server binaries and support files on a
Windows Server. The NAS 8000 is used to store non-system SQL database(s), data files and/or transaction
logs.

addressing the NAS 8000 from the SQL Server

There are two methods of providing access to the NAS 8000 shares from the SQL Server system. The
preferred and most reliable method is to use the Universal Naming Convention (UNC) names to specify the
paths to the NAS 8000 share(s). A second method is to use a "mapped network drive" to provide access to
the desired share(s) on the NAS 8000. Please carefully read the sections that follow for important
information concerning these two different methods for specifying storage paths for SQL Server to the NAS
8000.

Universal Naming Convention

Universal Naming Convention is the preferred and strongly recommended method for specifying the paths
for all NAS 8000 storage. UNC names are specified as follows: \\nas8000_network_name\share_name
or
\\ip_address_of_nas8000\share_name. If there is a Name Server configured on the network and the
information from the NAS 8000 has been correctly configured into the name server, then use of the NAS
8000 network name rather than the IP address may present an environment which is easier to maintain.
For instance, if the IP address is used (rather than the NAS 8000 network name) and for whatever reason,
the IP address of the NAS 8000 had to be changed, then all occurrences of the IP address would need to
be updated, individually. This includes in all database access scripts and in all database descriptions. This
7