Hey Jo:
Well, I have to tell ya, to really get to the root of the problem, one would need access to the site. This isn't the kind of thing that can be solved in a forum. The first thing you should do is contact the module provider of the photo album module (did you buy it or was it free?), and see if you can get them to help. It's also not clear, since you mention you have two sites, one of which is SQL 2K5 and the other SQL 2K...exactly which of these sites is having the problem.
I also highly unrecommend you run stored procedures, based on some advice, without learning more about SQL 2005. The issue arises that someone says, 'oh, well, just run this stored procedure here, and it'll fix your problem!'. And then it doesn't fix the problem, but perhaps exacerbates it...in which case, the advisor disappears. ;-) It does sound like you are trying to restore a SQL 2K database to SQL 2K5, and that isn't going to work. There is a way of converting a database to 2k5 from 2k, but I don't know if this includes a backed-up database file. What you should try to do is to go visit a local .NET users group, and see if someone there can help you. You can also try to restore the database in Enterprise Manager for 2K, and then read up on how to upgrade the database to 2K5.
I know this isn't much help. But you're getting into areas of DNN that require database expertise. Whenever I don't know something, I try to figure out 'who can I call?' :-) But if I were less technically knowledgeble, and used DNN because it solves my business problem, I would take a laptop with the site on it to a .NET user group meeting, or better yet a .NET user group with a DotNetNuke spin-off group in your area, and see if you can get someone to take a look at the problem and recommend what to do.
As far as the image pointing to the wrong folder, fixing it all depends on what the aspx file (or ascx file if it's a control) is doing. If it is using an image control, adding a ~/ to the start of the path will help build the path correctly. However, this doesn't appear to be the problem...it looks like this missing folder was created after this database was restored? What you could do is to copy the images to the path that the properties file is expecting (/Portals/0). Of course, this may make a mess of that folder, but at least the images will show up.
What I do for database backup is use the backup scheduling capabilities in 2000 and SQL 2005. What I also do is what Lee recommends--I have a local copy of my sites, do all my development on the local copy, and only add modules after testing them on my local server.
And no matter what the module developer says about no one else having a problem, if removing that module fixed the speed issue, then that module is, in fact, the culprit. It's unfortunate, but there are lots of ways to create a poorly designed module, by doing things like not closing connections, not disposing of classes and variables, and many other things. Since the log file was humongous, it's very possible that there's info in that log file that shows issues from the module running. The other thing you could do is show the module developer a copy of the site *with* the photo module running and a copy *without* that module in it, and let them see the difference. It may be too late for all this, but in the future, these are ways to show a module developer that there is an issue with the module. I'm sure they would fix it if they knew there were problems, right? Some people are more amenable to listening than others, but I doubt that anyone would not want to fix a problem if there is a way to make them aware of it.
Hope this helps... |