Go: Web page script Execution timeout problem, MSSQL time-out of the palliative cure means

Use Alterdatabase to set a smaller filegrowth or set a new size.

Workaround: 1 (the root of the problem)--this method has not been validated. Who weak tried to tell. Thank you
I'm actually a database file that timed out when it was added. Instead of flat, the specific SQL statement time-out is often assumed. Set the filegrowth to a lower value, OK everything is restored.

The setup of FileGrowth is to set the following window for the properties of the database in Enterprise Manager of the database:

This timeout may occur once your database file is large. Don't simply assume that the server is under too much pressure. Maybe it was one of your settings that caused the timeout.

When the database file is full, the default SQL Server automatically increases the 10% size of the original database file for continued use.

If your database file is very large, this time the trouble comes, CSDN forum This problem is to increase the database file time out.

Then all the other new operations will be reported time-out, which is actually CPU, memory consumption is very very low.

Solution 2: (workaround)---This can be added when big data operation is possible with the validation

Add a sentence after set Conn=server.createobject ("Adodb.connection")

conn.commandtimeout=300

Go: Web page script Execution timeout problem, MSSQL time-out of the palliative cure means