SQL Timeout solutions are sometimes not setup issues _mssql

Server.scrīpttimeout, the default value is 90 seconds.
To enlarge it, add a sentence to your ASP file, as follows:
server.scrīpttimeout=999,
Set the page timeout to 999 seconds.

Initially I only set server.scrīpttimeout,
However, there will still be a timeout error, regardless of its value set in Chengdu how big.
After seeing a post in the community, referring to the CommandTimeout attribute,
So I looked at the Option Pack document and there was timeout.

Both the connection object and the command object have a CommandTimeout attribute.
The default is 30 seconds, if you have a time-consuming query or data processing,
It's easy to time out. To enlarge it, it is also easy to create an object after the
Set its properties as follows:
Con.commandtimeout = 999,
Set to 999 seconds, where con is a connection object.
If set to zero, will infinite wait, without this timeout limit.

The command object does not inherit this property of connection,
So also set the CommandTimeout property separately for the command that might timeout.

Finally, IE also has a timeout setting, 5 minutes from the server can not get data, also timed out.
This situation may be rarely encountered,
But when I save the results of the more than 1.1 million query as an MDB file,
I met him. (For the preservation method, please refer to a post in the Essence area.)
Workaround: (Refer to Q181050 in Microsoft KB)

Before doing the IC trading network because the data is too large, super 10 million, add a memory solution
1. IE to 4.01 SP1 above version.
2. Hkey_current_usersoftwaremicrosoft in the registry
In Windowscurrentversioninternet settings
Add a DWORD type ReceiveTimeout, the value set to be like 8 9.
3. Restart Computer.