Re: SQL Server 2000 SP4 - ODBC Performance issues
- From: Sue Hoegemeier <Sue_H@xxxxxxxxxxxxx>
- Date: Sun, 16 Oct 2005 15:02:13 -0600
It may not necessarily be an ODBC performance issue. Have
you tried looking at the execution plans for the queries
that are causing the problems?
You can use profiler to monitor the activity and identify
the worst performers, CPU use if that's the concern.
They query plans may have changed on SP4 and that could be
what's contributing to your issue.
You may also want to monitor the waittypes by querying
sysprocesses and wait stats using dbcc sqlperf(waitstats).
-Sue
On Wed, 5 Oct 2005 03:30:02 -0700, "Deanw"
<Deanw@xxxxxxxxxxxxxxxxxxxxxxxxx> wrote:
>Server is quad processor with 3 gig of RAM of whcih 2 gig is allocated to SQL.
>Last weekend we upgraded the SQL from SP2 to SP4, since then the ODBC
>queries trhey run via MSQUERY appear to be really hitting the CPU and
>sqlserver.exe is consuming up to 90% of the CPU. It is looking very much like
>the ODBC queries are the cause, they reference a view in the database that is
>made up of a number of selects from a number of databases joined by the union
>command. Is anyone aware of any issues with SP4 that might effect this ? The
>DB server is now using MDAC 2.81 since the upgrade and we have ensured the
>clients are also using MDAC 2.81 as well
.
- Prev by Date: Re: ODBC SQL Server Driver Protocol error in TDS stream
- Next by Date: question on views
- Previous by thread: Re: ODBC SQL Server Driver Protocol error in TDS stream
- Next by thread: Re: SQL Server 2000 SP4 - ODBC Performance issues
- Index(es):
Relevant Pages
|
Loading