What should I do if SQL Server 2000 backup is very slow?

1. There may be too many hard disk fragments, tidy it up, or back up it in other hard disks;

2. Make sure that no other applications are using the database;

3. Shrink the database;

4. Detect and kill viruses, etc.;

5. Back up after restart;

Try this one, I've used, detach first, copy first, and append back.

Database backup should be fast, huh? Are you backing up on your own computer or on a server? If so, there should be a problem on the server? It won't be so slow!

Whether you are backing up remotely or locally, if the local backup should not be slow, it may be poisoned, do the system to see.

It should be done when the volume of traffic is low and the traffic is free. Or put it on a different disk.

The read and write speed of the hard disk will affect the write speed of the input library, and see if your mysql has added a lot of indexes, or whether it is a remote database... Hard disk, CPU, memory, network, and MySQL configuration all have an impact on execution speed.

SQL query in the database is not fast, if not, you need to optimize the statement, see whether to use the query code residual citation, etc.

If the query in the database is answered quickly, then optimize your program** to go.

There are two things to consider.

1. The database file is too large, and the data file (etc.) generally does not have action, so you can check whether the log file (LDF) has room for shrinkage, and if so, you can consider shrinking the log file.

2. If the CPU allows, the backup can be compressed backup, which can effectively reduce the size of the backup file.

1. Set the database to simple mode.

2. Right-click the database [Task] [Shrink] [Database].

3. Back up again completely and see.

1. Delete logs.

2. Correct the data table, and move the data to the corresponding data backup table after the end of the monthly attendance, so that only the data that has not been summarized for attendance is retained in the data table, that is, the current data.

Others, which may be related to the design of your system.

I don't know how you added the data.

It doesn't seem to be used.

Instead, you should use:"insert into .."That's no problem.

Now that the index is added, let's look at the way you write the SQL statement when you access, such as looking up only the data you need, not all the data.

The database log file is too large, just delete some.

Create an adoconnection, and then use this conn to execute the SQL statement to insert the data, and the specific writing is conn is the adoconnection that you have established and connected to, and the SQL statement is the insert data statement that you have spelled out.

Our company's backup time is basically once a day, and the complete backup is generally 2 o'clock in the morning, and the server is used by fewer people, and the backup is completed in about 10 minutes (the backup time is related to the performance of the server).

If your company's daily data volume is relatively large, it is recommended to complete the backup every day when there are few people.

1.The data backup policy can be as follows:

Full backups are made once a week.

Incremental backups are made once a day.

Transaction logs are backed up every 1 hour or 30 minutes.

2.In addition, the hardware should also be configured for security

For example, the twin machine ah or something.

1、shutdown

2. Copy the data file.

3. Restart the service.