| Author |
 Topic  |
|
fav
Starting Member
Spain
7 Posts |
 Posted - 19 April 2002 : 05:45:29
|
Firstly, I apologize for not answering soon.
Then, I have to tell you that I followed the line started by ruirib:
quote:
Ok, I'm just guessing here, but I'm on lucky streak today ().
What driver are you using? Please post your connection string.
and then I found a topic called "Speed problems after upgrading!" from klubdj where ruirib was advising to change the connection string quote:
Try this connection string. It should improve performance, although I cannot quantify it.
strConnString = "Provider=SQLOLEDB;Data Source=YourServer;Initial Catalog=YourDB;User ID=YourID;Password=YourPasswd;"
and I did... and so far it looks that my problem dissapeared.
I have noticed thoug, that if I change back to my old string it keeps working until I create a new user and I try to view his profile. In this case my problem comes back but I change back to the CS suggested by ruirb and disssapears again.
So..., T H A N K S to you all.
|
 |
|
|
ruirib
Snitz Forums Admin
Portugal
26364 Posts |
Posted - 19 April 2002 : 06:36:32
|
Well, I had a feeling that could be the cause, indeed. The more I see it the more I become convinced that you should always use OLEDB drivers.
Fav,
Just keep the OLEDB driver. No need to change it. It's obvious that this problem of yours is related to the ODBC drivers. I don't think this is a forum bug. If it were the OLEDB drivers should fail there also.
I'm just curious whether the problems that have been related about the order that you need to use to retrieve fields in a SQL insctruction couldn't be overcome by using the OLEDB driver as well...
Never mind, what really matters is that the problem is satisfactorily solved.
-------------------------------------------------
Installation Guide | Do's and Dont's | MODs |
|
|
|
Gremlin
General Help Moderator
New Zealand
7528 Posts |
Posted - 19 April 2002 : 10:15:44
|
Its not really a case of forum bugs but ODBC short commings that cause the timeouts imo, shouldnt have to code 'around' your odbc driver :(
www.daoc-halo.com |
|
|
|
ruirib
Snitz Forums Admin
Portugal
26364 Posts |
Posted - 19 April 2002 : 10:57:44
|
quote:
Its not really a case of forum bugs but ODBC short commings that cause the timeouts imo, shouldnt have to code 'around' your odbc driver :(
www.daoc-halo.com
Sorry Gremlin, I don't think I understood your comment. What would you suggest to overcome this situation?
In the past few days I met a significative number of problem situations, all of them related to ODBC drivers used with Access or SQL Server. I saw problems manifested by very high execution times, by error messages regarding parameters missing or servers hanging. All of them were overcome simply by changing to OLEDB drivers. What's more ODBC drivers add an extra layer, since ADO will use an OLEDB driver for ODBC, to be able to access a database using ODBC.
So, my view is that you really should use OLEBD instead ODBC whenever you can. Not only because it can spare you some problems, bu also because it will be faster.
-------------------------------------------------
Installation Guide | Do's and Dont's | MODs |
|
|
|
Gremlin
General Help Moderator
New Zealand
7528 Posts |
Posted - 20 April 2002 : 11:41:21
|
There are pleanty of documented 'issues' with the ODBC drivers, and most of them can be worked around by altering your code, order of your selects etc etc. My point was as a developed you shouldnt have to, the ODBC layer should be something you don't really need to care about.
Using the OLEDB drivers which have far fewer problems is normally a much simpler way to fix the problmes as you well know :) plus as you point out they are inherintly faster.
www.daoc-halo.com |
|
|
|
ruirib
Snitz Forums Admin
Portugal
26364 Posts |
Posted - 20 April 2002 : 12:29:20
|
quote:
There are pleanty of documented 'issues' with the ODBC drivers, and most of them can be worked around by altering your code, order of your selects etc etc. My point was as a developed you shouldnt have to, the ODBC layer should be something you don't really need to care about.
Yes, I agree with you, you shouldn't need to worry about any layers upon which ADO needs to rely on. The point of ADO is to allow transparency in your database access. The fact that the ODBC drivers seem to have to many issues to be solved really difficults this.
From what I've seen here in these last few days, I'll only use them, from now on, whenever OLEBD drivers won't be available.
-------------------------------------------------
Installation Guide | Do's and Dont's | MODs
Edited by - ruirib on 20 April 2002 12:33:16 |
|
|
|
putimeswebmaster
New Member
67 Posts |
Posted - 12 May 2002 : 21:44:05
|
I just switched to a dedicated server at my host and am experiencing the same or very similar problems. Snitz 3.3, Win2k, Access DB.
We have about 3,400 members at this point. We were working fine for a year or so, until we needed a dedicated server.
We migrated to a dedicated server and voila', about every 3 hours, the CPU peaks on dllhost.exe activity.
We have not ascertained exactly what script is running that causes this. Our odbc connect string:
strConnString = "Provider=Microsoft.Jet.OLEDB.4.0;Data Source=" & Server.MapPath("/dbdir/database.mdb") '## MS Access 2000 using virtual path
Any ideas?
Pop Up Times Webmaster
http://www.popuptimes.com |
|
|
|
ruirib
Snitz Forums Admin
Portugal
26364 Posts |
Posted - 12 May 2002 : 22:00:46
|
If you need a dedicated server for the site I'd say you probably should upgrade from Access to SQL Server also, admiting that the problem is database related. Just make sure that your server has the latest MDAC, since you are already using and OLEDB driver (no, that's not an ODBC connect string...).
You can also try to maybe have a look at your server log to see what was the last script to be executed. Maybe that will enable you to find the culprit...
-------------------------------------------------
Installation Guide | Do's and Dont's | MODs |
|
|
|
putimeswebmaster
New Member
67 Posts |
Posted - 13 May 2002 : 00:24:24
|
I agree with the SQL server option, however due to financial reasons it may not be an option. Our database is currently 66MB. Not too bad really.
Pop Up Times Webmaster
http://www.popuptimes.com |
|
|
|
Deleted
deleted
4116 Posts |
Posted - 13 May 2002 : 00:46:15
|
quote:
I agree with the SQL server option, however due to financial reasons it may not be an option. Our database is currently 66MB. Not too bad really.
Pop Up Times Webmaster
http://www.popuptimes.com
A very good size if it is really working good. I hope you compact it from time to time. Having so much posts in that period means you can have a lot of users online at the same time. Do you know how many there are simultaneously accessing the forums?
Think Pink
==> Start Internationalization Here |
|
|
|
putimeswebmaster
New Member
67 Posts |
Posted - 13 May 2002 : 01:04:44
|
Simultaneous users can get as high as 400 - 500.
Daily visitors spending 2 or more hourse is ~1,500
I archive posts older than 1 month and delete archive posts older
than 3 months on most of my forums.
This dllhost problem is killing me.
A lot of traffic indeed.
Pop Up Times Webmaster
http://www.popuptimes.com
Edited by - putimeswebmaster on 13 May 2002 01:12:31 |
|
|
|
ruirib
Snitz Forums Admin
Portugal
26364 Posts |
Posted - 13 May 2002 : 04:37:11
|
Well the problem with your database is not the size, it's Access's ability to handle a large number of simultaneous users. Access will never handle that large number of users well (even if I'm admiting that not all of them can be at the forum at the same time).
So, if on one hand I understand that SQL Server may not be financially viable, on the other hand Access may not be technically viable.
Anyway, the current problem may not have a direct relation to Access, becau it looks weird that the problem should only manifest itself when you changed to a dedicated server. Can it be a problem with the server itself? You need to track down the cause for this problem. Have you taled to your host?
On another note, if you have finantial limitations, maybe you should consider MySQL. It's free, it will handle a lot more simultanoeus users than Access, although migration can be a difficulty (that can be overcome).
-------------------------------------------------
Installation Guide | Do's and Dont's | MODs |
|
|
|
putimeswebmaster
New Member
67 Posts |
Posted - 13 May 2002 : 14:14:38
|
Our host is trying to help out. I just finished a converions to SQL server. Hopefully this will cure things.
I will check back in with our solution.
Pop Up Times Webmaster
http://www.popuptimes.com |
|
|
|
Topic |
|
Topic Locked
