Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

Re: Problem profiling SQL 2000 server from 2008 profiler

21 views
Skip to first unread message

Erland Sommarskog

unread,
Mar 10, 2009, 7:20:06 PM3/10/09
to
tomf84 (tom...@discussions.microsoft.com) writes:
> I am trying to run the Tuning profile in SQL Server Profiler 2008
> against an SQL Server 2000 database, but I get the following error
> message when I try to start the trace:
>
> ---------------------------
> SQL Server Profiler
> ---------------------------
> Failed to start a trace.
> [Microsoft][SQL Server Native Client 10.0]Datetime field overflow.
> Fractional second precision exceeds the scale specified in the parameter
> binding. (State 22008) (Code 0)
>
> ---------------------------
> OK
> ---------------------------

It works for me. Did you add any filter to the trace?

--
Erland Sommarskog, SQL Server MVP, esq...@sommarskog.se

Links for SQL Server Books Online:
SQL 2008: http://msdn.microsoft.com/en-us/sqlserver/cc514207.aspx
SQL 2005: http://msdn.microsoft.com/en-us/sqlserver/bb895970.aspx
SQL 2000: http://www.microsoft.com/sql/prodinfo/previousversions/books.mspx

dwaine

unread,
Apr 3, 2009, 3:22:01 PM4/3/09
to
sorry, forgot to include profiler version info (copy info on help about was
the greatest invention since rollback!)

SQL Server Profiler 10.0.1600.22
Microsoft Data Access Components (MDAC) 2000.085.1132.00
(xpsp.080413-0852)
Microsoft MSXML 2.6 3.0 4.0 5.0 6.0
Microsoft Internet Explorer 6.0.2900.5512
Microsoft .NET Framework 2.0.50727.3082
Operating System 5.1.2600

"dwaine" wrote:

> "Erland Sommarskog" wrote:
>
> > tomf84 (tom...@discussions.microsoft.com) writes:
> > > I am trying to run the Tuning profile in SQL Server Profiler 2008
> > > against an SQL Server 2000 database, but I get the following error
> > > message when I try to start the trace:
> > >
> > > ---------------------------
> > > SQL Server Profiler
> > > ---------------------------
> > > Failed to start a trace.
> > > [Microsoft][SQL Server Native Client 10.0]Datetime field overflow.
> > > Fractional second precision exceeds the scale specified in the parameter
> > > binding. (State 22008) (Code 0)
> > >
> > > ---------------------------
> > > OK
> > > ---------------------------
> >
> > It works for me. Did you add any filter to the trace?
> >
>

> This is repeatable for me. Standard trace template (or any template).
> don't touch a thing EXCEPT for selecting "Enable Trace Stop Time". This is
> the culprit.
>
> Only throws error when running against 2000. 2K5 and 2K8, no error.
>

Erland Sommarskog

unread,
Apr 25, 2009, 6:02:58 PM4/25/09
to
dwaine (dwa...@nospam.nospam) writes:
> This is repeatable for me. Standard trace template (or any template).
> don't touch a thing EXCEPT for selecting "Enable Trace Stop Time". This
> is the culprit.
>
> Only throws error when running against 2000. 2K5 and 2K8, no error.

I see. Yes, that's definitely. There has been some changes with the
datetime data types in SQL 2008. That probably has something to do with it.

I tested this in SQL 2008 SP1 as well, but the issue persits.

I've filed a bug for this:
https://connect.microsoft.com/SQLServer/feedback/ViewFeedback.aspx?FeedbackID=435233

0 new messages