Yes. I even performed a backup/restore from the development server to the
test cluster. The web application is working, and it is using the database on
the cluster, but I'm seeing very different results from the Profiler.
It's like the events are not being passed up to the cluster, but even if I
run the Profiler from the virtual server I get the same results since I'm
connecting to the same named instance.
And I do see events with the LoginName that the app uses.
"Uri Dimant" wrote:
> Andrew
> Are you sure that you tested against the same application and the database's
> structure are the same?
>
>
>
> "Andrew Hayes" wrote in message
>
> > Hi all,
> >
> > Just hoping that someone could shed some light on something strange with
> > profiler.
> >
> > I'm doing some performance and bottleneck testing of a new app that uses a
> > SQL Server 2005 SP2 cluster on the backend. When I run a trace against the
> > development server (which is a non-clustered SQL Server 2005 SP2), I can
> > see
> > the RPC:Completed events for the exec sp_executesql N'....' for various
> > executed command texts. However, when I run the same trace against the
> > clustered DB I get none of those events, although I do get RPC:Completed
> > events for other execs.
> >
> > Both traces use the Standard (default) template. The only difference is
> > one
> > trace connects to the named instance of the development server, while the
> > other trace connects to the named instance of the virtual server on the
> > cluster.
> >
> > Are there configuration settings I need to change?
>
>
> >> Stay informed about: SQL Server 2005 SP2 Profiler Operates Differently? 
FAQ
Search
Profile
Private Messages
Log in
