| Author |
 Topic Search  Topic Options
|
WebWiz-Bruce 
Admin Group
Web Wiz Developer
Joined: 03 September 2001
Location: Bournemouth
Status: Offline
Points: 9844
|
 Post Options
 Thanks(0)
 Quote  Reply
 Posted: 15 April 2012 at 4:56pm |
The link to the image did not work, but I am guessing the time out is a database timeout rather than a script timeout.
You would need to increase the database query timeout on the SQL Server so that the new fields can be added to the tables.
|
|
|
 |
hummelmose
Newbie
Joined: 05 November 2009
Status: Offline
Points: 18
|
Post Options
Thanks(0)
Quote Reply
Posted: 15 April 2012 at 5:03pm |
It's the same error described above.
http://dl.dropbox.com/u/65950/bruce.png
http://dl.drop.com/u/65950/bruce.png
As written I've set timeout to 0 (no timeout)
|
|
WebWiz-Bruce
Admin Group
Web Wiz Developer
Joined: 03 September 2001
Location: Bournemouth
Status: Offline
Points: 9844
|
Post Options
Thanks(0)
Quote Reply
Posted: 15 April 2012 at 5:09pm |
Then my previous reply to you was correct, this is a database timeout and you need to have the database admin increase the query timeout on the database server.
When new fields are added to a table SQL Server will have to rebuild the table with the new fields. This can take some time and if the database is quite large it can take longer than queries are allowed to take giving the database timeout that you see.
This is database server side rather than on the web server side, so increasing the script timeout would not fix the issue.
Failing that you would need to attempt to create the new fields in the tblThread table manually.
The fields that you would need to create the tblThread are:-
1. Answer - datatype = bit - default value = 0 2. Thanks - data type = integer - default value = 0 |
|
|
|
hummelmose
Newbie
Joined: 05 November 2009
Status: Offline
Points: 18
|
Post Options
Thanks(0)
Quote Reply
Posted: 15 April 2012 at 5:12pm |
I'm trying to attach images. But you wont let me.
Look at my SQL Server settings:
http://dl.dropbox.com/u/65950/bruce2.png http://dl.dropbox.com/u/65950/bruce3.png
So I still can't understand why I get a timeout. If you mean something else, please explain what else to set different on the sql server
|
|
WebWiz-Bruce
Admin Group
Web Wiz Developer
Joined: 03 September 2001
Location: Bournemouth
Status: Offline
Points: 9844
|
Post Options
Thanks(0)
Quote Reply
Posted: 15 April 2012 at 5:17pm |
You will need to create the new fields in tblThread manually using the info I gave in the previous post as there is nothing that can be changed in the upgrade script to try and fix this issue, your database is simply to large for web server side upgrade scripts to work.
The other tables will be upgraded fine, it will just be tblThread that you need to manually update.
|
|
|
|
hummelmose
Newbie
Joined: 05 November 2009
Status: Offline
Points: 18
|
Post Options
Thanks(0)
Quote Reply
Posted: 15 April 2012 at 5:37pm |
 WebWiz-Bruce wrote:
You will need to create the new fields in tblThread manually using the info I gave in the previous post as there is nothing that can be changed in the upgrade script to try and fix this issue, your database is simply to large for web server side upgrade scripts to work.
The other tables will be upgraded fine, it will just be tblThread that you need to manually update. |
'tblThread' table - Unable to modify table. Timeout expired. The timeout period elapsed prior to completion of the operation or the server is not responding.
Sorry. No cigar. It was done directly on the SQL server via Admin interface.
|
|
rune
Groupie
Joined: 09 December 2010
Status: Offline
Points: 40
|
Post Options
Thanks(0)
Quote Reply
Posted: 15 April 2012 at 6:22pm |
|
Sounds like some other program has a lock on the table.
The brute-force way to fix that is to restart the sql server.
Bruce: the database does not normally time out just because the table is big. Only if it is overloaded _and_ has timeout specially configured by the admin. On an unloaded server, you can modify a table with hundreds of thousands of rows in a few seconds.
|
|
hummelmose
Newbie
Joined: 05 November 2009
Status: Offline
Points: 18
|
Post Options
Thanks(0)
Quote Reply
Posted: 15 April 2012 at 8:12pm |
rune wrote:
Sounds like some other program has a lock on the table.
The brute-force way to fix that is to restart the sql server.
Bruce: the database does not normally time out just because the table is big. Only if it is overloaded _and_ has timeout specially configured by the admin. On an unloaded server, you can modify a table with hundreds of thousands of rows in a few seconds.
|
It's a fresh restore, so no one has lock on the database.
|
|
