833 problem

[majer2295]

The database server itself was run on virtualized vmware, and was later moved to the company's private cloud through mirroring, and then the problem of SQL Server 833 occurred frequently.

[#2]

@majer2295 , this is an English spoken forum, so please post the error message as text and in English.

Is it this error:

SQL Server has encountered %d occurrence(s) of I/O requests taking longer than %d seconds to complete on file [%ls] in database id %d. The OS file handle is 0x%p. The offset of the latest long I/O is: %#016I64x. The duration of the long I/O is: %I64u ms.

Simply means your I/O storage is to slow.

[#3]

@olafhelper 

There are no problems after the io test. After the database migration, no index reconstruction and statistical information update were performed. However, due to the large amount of data, the production environment still dare not perform index reconstruction online. Could you please help me see if it is necessary to perform index reconstruction?