August 24, 2007 at 7:44 am
I've noticed that most queries run significantly slower the first time I run them in the morning, after the first time they've run the results shoot back almost instantly. I've tested this with a variety of queries from very simple 'select count('x') from inventory' to very complex (nasty query with five table joins, group by and multiple columns in the where clause) and the results seem the same. We're not sure what could cause this. We've tried messing around with indexes but the execution plan seems to be efficient and logical based on the indexes we have.
The only idea I could think of was some sort of caching of results performed by SS. Is this possible?
We'd like to figure out a way to eliminate the long run times first thing in the morning, anyone have any insight on this?
Thanks in advance for you help,
Ben
August 24, 2007 at 8:51 am
We discovered that running a full backup at night causes the issue. Does anyone know why running a backup would cause a query to run slow?
Viewing 2 posts - 1 through 1 (of 1 total)
You must be logged in to reply to this topic. Login to reply