Re: sql2k5 performance
- From: "Andre" <nospam@xxxxxxxx>
- Date: Tue, 12 Jun 2007 07:32:20 -0700
Yes, I update stats daily. The db is in 90 compatibility mode. The query
plans between Production (SQL2k) and Dev (SQL2k5) they look similar, but not
identical. However, the bulk of the cost is still in a clustered index scan
(yes, I know that's not optimal, but when the proc works in 1 second, I'm
not too concerned). I do see that the old query plan has parallelism, while
the new one does not. But since 0% of the cost is there I don't know if
this makes a difference or not. What specifically should I look for in the
query plan? And what is it about SQL 2k5 that would make this soooo much
slower? I'd really like to understand the difference.
Thanks, Andre
.
- Follow-Ups:
- Re: sql2k5 performance
- From: Andrew J. Kelly
- Re: sql2k5 performance
- References:
- sql2k5 performance
- From: Andre
- Re: sql2k5 performance
- From: Andrew J. Kelly
- sql2k5 performance
- Prev by Date: Re: sp_attach_db on Vista causes read only problems
- Next by Date: Re: sp_attach_db on Vista causes read only problems
- Previous by thread: Re: sql2k5 performance
- Next by thread: Re: sql2k5 performance
- Index(es):
Relevant Pages
|