Viewing 5 posts - 1,216 through 1,220 (of 1,220 total)
Thanks, Vladan, I remember what it was now. It was LIKE and IN, IIRC, that forced a table scan. My bad. I blame it on being sick since last Wednesday....
-----
[font="Arial"]Knowledge is of two kinds. We know a subject ourselves or we know where we can find information upon it. --Samuel Johnson[/font]
February 17, 2004 at 2:06 pm
Sorry, I don't have a quick answer for what you're looking for. All I can suggest is that there is a world of information looking at the system tables and...
-----
[font="Arial"]Knowledge is of two kinds. We know a subject ourselves or we know where we can find information upon it. --Samuel Johnson[/font]
February 17, 2004 at 9:39 am
I recall having read that using BETWEEN automatically forces a table scan. I don't recall where, but I'd break it up using two >= and <= statements and see if...
-----
[font="Arial"]Knowledge is of two kinds. We know a subject ourselves or we know where we can find information upon it. --Samuel Johnson[/font]
February 17, 2004 at 9:08 am
I wrote a script several years ago that might help, I wrote it for 6.5 for the swynk.com site. <g>
Anyway, it's at http://www.databasejournal.com/scripts/article.php/1546401, I hope it helps. You'll need...
-----
[font="Arial"]Knowledge is of two kinds. We know a subject ourselves or we know where we can find information upon it. --Samuel Johnson[/font]
February 17, 2004 at 9:01 am
Indexes were also my first thought. Check to see that your indexes are built well (logically) and that whatever stored procedures are accessing them are actually hitting them through SQL...
-----
[font="Arial"]Knowledge is of two kinds. We know a subject ourselves or we know where we can find information upon it. --Samuel Johnson[/font]
February 17, 2004 at 8:52 am
Viewing 5 posts - 1,216 through 1,220 (of 1,220 total)