How to solve "device activation error" in SQL Server 2000

Data Operations in databases are an important skill. data recovery and restoration are also common. I wonder if you have encountered an error message such as "device activation error during database recovery, please use the with move option to mark the valid location of the file? I wonder if you still encounter this situation: When you restore the database, you find that in the Enterprise Manager, the operation: all tasks --> restore the database --> select "restore from device, find the path of the backup document and force restore. Error: device activation error. Use the with move option to indicate the valid location of the file. This article will explain how to solve this error.

Solution: Right-click "Database" (note that it is not a specific database) -- all tasks -- Restore database -- select "restore from device, select the name of the database to be restored, and on the tab, select force Restore database on the most existing database, and then modify the physical path of the database after restoration below, if this path exists as a path, otherwise the above error will occur. You do not need to change the logical file name. It turns out to be a path error.

Another Error solution may be used later.

How to change the owner of the User table of SQL server 2000 to dbo instead of the user name?

Method 1: Right-click the table and choose design table from the shortcut menu. In the previous small icon, click the last "condition constraint" and click the "table" page to change the owner.

Method 2: Execute the script directly, log on to the database with a system account or a super user, and then execute the following statement:



(Note: The second method can only be used once, and an error occurs when the second method is used)

Solution 3:

I believe that many of my friends have encountered this problem with a big head. Then, when searching for similar problems on the Internet, the solution is basically the same, and the results are the same, that is, they cannot solve the problem, I am also the first to grow my head for a few days. I have not solved the problem after installation or uninstallation N times. I am constantly exploring the differences between versions and database structures, later, I found a solution to the problem in a casual restoration database, as shown in the following figure (only use my solution to solve the problem, and use other types of signatures ):

Preparation: the SQL server 2000 file that has been backed up, with a suffix added to the file name (. bak, the backup of SQL server 2000 is generally suffixed like this)

SQL server 2000 installed;

Database restoration process:

1. Open "Enterprise Manager", find the database option, and create a new database (testdata );

2. Right-click the new database (testdata) and choose "all tasks"-> "Restore database". In the displayed dialog box, select "Slave Device ", click "select device" to find the data backed up earlier,

The following dialog box appears after a continuous "OK:

3. Click "options ",

In the displayed dialog box, select "Force restore on existing database". The most important content is as follows: Ignore the two files under the logical file name, for more information, see "move to physical file name". You must select the installation directory of SQL server 2000 for the two options, I am wrong because I set its directory to drive D (drive D is where I install the management directory). That is to say, "physical file name" must be the same as the installation directory of SQL server2000; refer: