| Author |
 Topic  |
|
danielwym
Starting Member
Hong Kong
16 Posts |
 Posted - 29 March 2004 : 23:47:56
|
My forum engine already contains 320,000 records.
But it always occurs below errors once users access to the topics:
Microsoft OLE DB Provider for SQL Server error '80004005'
Timeout expired
I have try to set longer scipt timeout & add response.flush to see any improvement. But unfortunately, it doesn't. Any recommendation? Urgent!!!!!!!!!!!!!!!!!!!! |
|
|
Jeepaholic
Average Member
USA
697 Posts |
Posted - 30 March 2004 : 01:09:04
|
Hi...try to explain your situation a little better if you can. Some questions you can answer are:
1) Are you running your own server, or are you hosted?
2) What type of hardware are you running on?
3) How is the Recovery Model in SQL set? (Full, Simple, etc...)
4) When are you seeing this issue, exactly?
5) Is there a link we can see?
6) I assume you have 320,000 *posts*, when you say records? Just curious.
Some of these questions (and probably a lot more) will help the members here give you some better direction. |
Al Bsharah
Aholics.com
Jeepaholics Anonymous
Broncoholics Anonymous
Network Insight
|
 |
|
|
danielwym
Starting Member
Hong Kong
16 Posts |
Posted - 30 March 2004 : 03:37:00
|
quote:
Originally posted by Jeepaholic
Hi...try to explain your situation a little better if you can. Some questions you can answer are:
1) Are you running your own server, or are you hosted?
2) What type of hardware are you running on?
3) How is the Recovery Model in SQL set? (Full, Simple, etc...)
4) When are you seeing this issue, exactly?
5) Is there a link we can see?
6) I assume you have 320,000 *posts*, when you say records? Just curious.
Some of these questions (and probably a lot more) will help the members here give you some better direction.
|
|
|
|
HuwR
Forum Admin
United Kingdom
20595 Posts |
Posted - 30 March 2004 : 03:39:39
|
| an answer to the questions would have been helpful ! |
|
|
|
danielwym
Starting Member
Hong Kong
16 Posts |
Posted - 30 March 2004 : 03:41:03
|
1) the forum is running on its own server
2) PIII, NT4, SQL server 7.0
3) any realation to the timeout error? btw, i don't know.
4) When users access:
a. forum.asp
b. topic.asp
c. post.asp
sometimes it will hang & sometimes "timeout expired" error out.
5) internal development
6) yes. 320,000 posts.
Sorry for my poor explaination & really urgently need help. Thks so much!!!
quote:
Originally posted by Jeepaholic
Hi...try to explain your situation a little better if you can. Some questions you can answer are:
1) Are you running your own server, or are you hosted?
2) What type of hardware are you running on?
3) How is the Recovery Model in SQL set? (Full, Simple, etc...)
4) When are you seeing this issue, exactly?
5) Is there a link we can see?
6) I assume you have 320,000 *posts*, when you say records? Just curious.
Some of these questions (and probably a lot more) will help the members here give you some better direction.
|
|
|
|
danielwym
Starting Member
Hong Kong
16 Posts |
Posted - 30 March 2004 : 03:42:36
|
Sorry. Post wrongly.
quote:
Originally posted by HuwR
an answer to the questions would have been helpful !
|
|
|
|
HuwR
Forum Admin
United Kingdom
20595 Posts |
Posted - 30 March 2004 : 03:48:27
|
which of the connection string are you using in config.asp ?
How much RAM does your SQL server use ?
Is SQL and website on the same server ? |
|
|
|
danielwym
Starting Member
Hong Kong
16 Posts |
Posted - 30 March 2004 : 03:57:24
|
Thks for the quick response.
OLE DB should be.
No. Webserver & SQLServer are installed at seperate machine where SQL Server with 1G RAM.
quote:
Originally posted by HuwR
which of the connection string are you using in config.asp ?
How much RAM does your SQL server use ?
Is SQL and website on the same server ?
|
|
|
|
HuwR
Forum Admin
United Kingdom
20595 Posts |
Posted - 30 March 2004 : 04:08:15
|
Ok, sorry for all the questions, but will need a few more to get to the bottom of it.
1) what network protocol is your SQL server using ? (make sure it is TCPIP)
2)check your network for excessive traffic incase something is getting in the way (timeouts are more often than not caused by high network traffic)
3) can you query the sql server using Isql or something else from the client ?
It really shouldn't be necesary to change any of the timeout values from the forum code, sql timeouts are not generally related to the code, it is normally something not right with the system itself. |
|
|
|
danielwym
Starting Member
Hong Kong
16 Posts |
Posted - 30 March 2004 : 04:26:15
|
Thks so much for the help.
1) Yes. It should be TCP/IP
2) Sorry. Do you mean the timeout is caused by high network traffic? If yes, how can I check it?
3) I have wrote the SQL out and try to use the QA to run it. It returns result set with acceptable speed(few seconds).
Really thks.
quote:
Originally posted by HuwR
Ok, sorry for all the questions, but will need a few more to get to the bottom of it.
1) what network protocol is your SQL server using ? (make sure it is TCPIP)
2)check your network for excessive traffic incase something is getting in the way (timeouts are more often than not caused by high network traffic)
3) can you query the sql server using Isql or something else from the client ?
It really shouldn't be necesary to change any of the timeout values from the forum code, sql timeouts are not generally related to the code, it is normally something not right with the system itself.
|
|
|
|
HuwR
Forum Admin
United Kingdom
20595 Posts |
Posted - 30 March 2004 : 04:50:05
|
are you running a bog standard Snitz installation, or have you modified any of the code ?
Can you create a simple asp page to query the db, does this work ?
you can download a free network monitor (do a search on google) to check your network. |
|
|
|
danielwym
Starting Member
Hong Kong
16 Posts |
Posted - 30 March 2004 : 22:33:36
|
Hi HuwR,
Thanks for the reply. "Bog standard Snitz installation" means...
Btw, I will try to install a network monitor to check it. It seems SQL server loading quite high sometimes. Does this affect and thus those timeout error come out?
quote:
Originally posted by HuwR
are you running a bog standard Snitz installation, or have you modified any of the code ?
Can you create a simple asp page to query the db, does this work ?
you can download a free network monitor (do a search on google) to check your network.
|
|
|
|
Jeepaholic
Average Member
USA
697 Posts |
|
|
ruirib
Snitz Forums Admin
Portugal
26364 Posts |
Posted - 31 March 2004 : 06:31:13
|
| A timeout means that the SQL server did not respond in a given amount of time. A high server load will, of course, affect the ability of the server to respond to requests made to it. |
Snitz 3.4 Readme | Like the support? Support Snitz too |
|
|
|
danielwym
Starting Member
Hong Kong
16 Posts |
Posted - 31 March 2004 : 06:40:35
|
Thanks for suggestions all guys. I haven't modified the code except the config file and header,footer....
it seems the "timeout expired" errors will out when the SQL server loading nearly 100%. Any suggestions on both hardware and software to improve such situation?
Thanks all guys. |
|
|
|
HuwR
Forum Admin
United Kingdom
20595 Posts |
Posted - 31 March 2004 : 06:47:14
|
You shouldn't really be getting problems like that. What is the spec of the machine.
Try running some traces while navigating round the forum, you should be able to see what is causing the sql server to peak so high.
MS SQL is a very server hungry app, you should give it as much memory as you can get in the server, and assign as much as you can to SQL (do not use dynamic memory allocation) also, use a fixed swap file and ensure it is not on the same drive as your sql database. Multiprocessor machines give sql a real burst of energy, so would recomend at least a dual processor. Also, put as many hard drives in your machine as you can fit, and split the data and logfiles so they are on seperate drives. |
|
|
|
Topic |
|
Topic Locked
