November 10, 2004 at 12:50 am
Hi Guys,
Not sure about this.
We have a database that is backed up and restored onto laptops to be used for demonstration..that's fine.
This happens once a week.
However, all of a sudden a certain procedure is running extremely slow. All things point to the indexes on the table used in the procedure. But it's not conclusive...
I was just wondering what else could do this when the procedure was running fine ???
Any thoughts?
Many Thanks...Graeme
November 10, 2004 at 4:38 am
Hi
Have you had a look at the re-compilation of the SP ?, try dropping the SP and recreating it and after that drop and recreate your indexes.
cheers
November 10, 2004 at 5:32 am
just a thought....
use one of the DBCC commands ( DBCC checkdb )....
GKramer
November 10, 2004 at 9:35 am
Thanks for those suggestions.
One thing that has happened is that SQL 2K Standard has been replaced by SQL 2k Developer Edition on the laptop, and now the web based app running locally is running really slow for odd procedures. I was looking at SQL as a problem but could there be an issue with SQL 2K DE on a laptop....are there any settings that need to be configured so that it runs ok with IIS on XP.
Thanks again Guys
Graeme
November 10, 2004 at 11:58 am
update statistics could make a difference as well. I would look and making sure you hard set the memory allocation to make sure SQL Server doesn't try to hog all the memory away from IIS.
Wes
November 11, 2004 at 12:37 am
The memory allocation of SQL will be your first point then run a profile and monitor your SP's and the execution time of them. There is no engine difference beteen desktop and server editions. go through your db settings and make sure all settings are set to optimum like disable auto shrink, auto close, auto update stats but leave auto create stats.
small things add up and make a difference in the end.
Viewing 6 posts - 1 through 5 (of 5 total)
You must be logged in to reply to this topic. Login to reply