The SQL error 5144, SQL error 5145 usually appears while extending the data or transaction log files or during autogrowth operation for data or log files.

Here at Bobcares, we have seen several such SQL related issues as part of our Server Management Services for web hosts and online service providers.

Today we’ll take a look at the cause for this error and see how to fix it.

More about SQL error 5144, SQL error 5145

If the size of the data is extended or log file with a larger value or if the database performs autogrow operation to extend its database files with bigger value, then SQL Server takes longer time to perform such activities.

As a result, the SQL Server reports 5144 and 5145 errors in the Application Event Log and ERRORLOG in case autogrow of a database and/or transaction log file has timed out or has taken a long period of time to complete.

The 5144 error appears as below

Msg 5144
Autogrow of file ‘Data or Log file name’ in database ‘Database’ was cancelled by user or timed out after <n> milliseconds. Use ALTER DATABASE to set a smaller FILEGROWTH value for this file or to explicitly set a new file size.

The 5145 error appears as below

Msg 5145
Autogrow of file ‘Data or Log file name’ in database ‘Database’ took <n> milliseconds. Consider using ALTER DATABASE to set a smaller FILEGROWTH for this file.

Solution for SQL error 5144, SQL error 5145

Now let’s see the solution part of this error message.

• In order to avoid 5144, 5145 error messages we need to plan the file size growth carefully. Setting maximum database size will help in not performing frequent autogrowth operation.
• Don’t rely on autogrowth of files as a standard operation for obtaining more space in a file. Instead, plan the maximum database size and allow autogrowth to occur only in unplanned situations for space.
• Enabling Instant File Initialization helps to speed up data file size allocation.
• IFI(Instant File Initialization) does not work on transaction log files. So we can set log files in smaller chunks to avoid any time out the error or longer runs.
• Make sure the disk performance is good.

[Need any assistance in fixing SQL errors? – We’ll help you]

Conclusion

In short, this error occurs while extending the data or transaction log files or during autogrowth operation for data or log files. Today, we saw how to avoid this error.