Therefore, from a security perspective, we require all users to install the "SQL2000 database" in an independent partition, and the "SQL2000 database" must be run in the state of "ordinary user". The so-called "ordinary user" refers to a user without any permissions.
Why do we have to run "SQL2000 database" in the state of "ordinary user"? Because if you use "super administrator" or "local system user" to run "SQL2000 database", the server will be invaded. Therefore, for your server security, you must run the "SQL2000 database" in the "ordinary user" state. At the same time, you must set the corresponding permissions for the hard disk to run normally. For the permission settings of the hard disk, please refer to the following:
(Suppose your data is installed in E:\Program Files\Microsoft SQL Server\)
1. The root directory of E disk (E:\) requires the following permissions:
All permissions of "administrators"
All permissions of "System"
"Selection of folders/read data for SQL2000's running user (only applied to the current folder)" permission
"Read attributes" permissions
Permission to "read extended attributes"
"Read" permission
2. The database installation directory (E:\Program Files\Microsoft SQL Server\) needs to be
Next permissions:
All permissions of "administrators"
All permissions of "System"
All permissions of "SQL2000 Running User"
(Suppose your data backup directory is installed in F:\SQLBACK)
1. The root directory of the F disk (F:\) requires the following permissions:
All permissions of "administrators"
All permissions of "System"
"Selection of folders/read data for SQL2000's running user (only applied to the current folder)" permission
"Read attributes" permissions
Permission to "read extended attributes"
"Read" permission
2. The database installation directory (F:\SQLBACK) requires the following permissions:
All permissions of "administrators"
All permissions of "System"
All permissions of "SQL2000 Running User"
Special reminder: Whether it is the permissions installed on the E disk or the root directory of the F disk, you must set them according to the above operations, otherwise the database startup will fail. Many users often ignore it
After deciding on the setting of "root directory permissions", after setting up the "SQL2000 Running User", it was found that the SQL2000 database could no longer be started. If this happens to you
In addition, please follow the above instructions and reset the "root permissions" and the SQL2000 database can be started normally.
Additional Note: The "SQL2000 running user" mentioned here is the user set in the security in SQL 2000 Enterprise Manager----properties (default is System user). If you've seen it
"Out-Star Security Pack Video Instructions" should be changed to another user who has "default System User" to "no permissions", and this user who has "no permissions" is here.
Speaking of "SQL2000 running user".
The SQL2005 run user is at the beginning --Microsoft SQL Server 2005 --Configuration Tool --SQL Server Configuration Manager, select the QL Server 2005 service.
Select the "SQL Server (MSSQLSERVER)" property to set this account.
Why do we have to run "SQL2000 database" in the state of "ordinary user"? Because if you use "super administrator" or "local system user" to run "SQL2000 database", the server will be invaded. Therefore, for your server security, you must run the "SQL2000 database" in the "ordinary user" state. At the same time, you must set the corresponding permissions for the hard disk to run normally. For the permission settings of the hard disk, please refer to the following:
(Suppose your data is installed in E:\Program Files\Microsoft SQL Server\)
1. The root directory of E disk (E:\) requires the following permissions:
All permissions of "administrators"
All permissions of "System"
"Selection of folders/read data for SQL2000's running user (only applied to the current folder)" permission
"Read attributes" permissions
Permission to "read extended attributes"
"Read" permission
2. The database installation directory (E:\Program Files\Microsoft SQL Server\) needs to be
Next permissions:
All permissions of "administrators"
All permissions of "System"
All permissions of "SQL2000 Running User"
(Suppose your data backup directory is installed in F:\SQLBACK)
1. The root directory of the F disk (F:\) requires the following permissions:
All permissions of "administrators"
All permissions of "System"
"Selection of folders/read data for SQL2000's running user (only applied to the current folder)" permission
"Read attributes" permissions
Permission to "read extended attributes"
"Read" permission
2. The database installation directory (F:\SQLBACK) requires the following permissions:
All permissions of "administrators"
All permissions of "System"
All permissions of "SQL2000 Running User"
Special reminder: Whether it is the permissions installed on the E disk or the root directory of the F disk, you must set them according to the above operations, otherwise the database startup will fail. Many users often ignore it
After deciding on the setting of "root directory permissions", after setting up the "SQL2000 Running User", it was found that the SQL2000 database could no longer be started. If this happens to you
In addition, please follow the above instructions and reset the "root permissions" and the SQL2000 database can be started normally.
Additional Note: The "SQL2000 running user" mentioned here is the user set in the security in SQL 2000 Enterprise Manager----properties (default is System user). If you've seen it
"Out-Star Security Pack Video Instructions" should be changed to another user who has "default System User" to "no permissions", and this user who has "no permissions" is here.
Speaking of "SQL2000 running user".
The SQL2005 run user is at the beginning --Microsoft SQL Server 2005 --Configuration Tool --SQL Server Configuration Manager, select the QL Server 2005 service.
Select the "SQL Server (MSSQLSERVER)" property to set this account.