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

Profiler and filtering by database name

0 views
Skip to first unread message

nevada

unread,
Nov 4, 2002, 1:41:31 PM11/4/02
to
I'm trying to profile usage on one database. However, when I specify
the database name as a filter ("like myDB"), the profiler still
catches usage on all the databases. In addition, if one of my columns
in the trace is "DatabaseName" the column is in the trace, but no
database names appear in it.

Any ideas? This looks like a great tool if I can get it to work.

Thanks, NS

mj4ALL

unread,
Nov 4, 2002, 3:31:04 PM11/4/02
to
nevada wrote:

Try using the DBID

Erland Sommarskog

unread,
Nov 4, 2002, 6:36:01 PM11/4/02
to
nevada (nevada...@yahoo.com) writes:
> I'm trying to profile usage on one database. However, when I specify
> the database name as a filter ("like myDB"), the profiler still
> catches usage on all the databases. In addition, if one of my columns
> in the trace is "DatabaseName" the column is in the trace, but no
> database names appear in it.

That's some funny quirk of the Profiler. If you apply a filter on a
column, the Profiler will still include events where this columns is
blank.

The suggestion to use dbid instead may be worth investigating; this
column may be populated more often.


--
Erland Sommarskog, SQL Server MVP, som...@algonet.se
I support PASS - the definitive global community for SQL Server
professionals - http://www.sqlpass.org
The PASS Community Summit is in Seattle Nov 19-22, I'll be there. And you?

nevada

unread,
Nov 5, 2002, 10:31:58 AM11/5/02
to
Using the Database ID does work. I'd still like to filter by name if possible.

Thanks, NS

Darren

unread,
Nov 6, 2002, 2:51:27 PM11/6/02
to
Also you should try to make sure have enough columns. I know some columns
are dependent on other columns being there.

I think DB Name is dependent on Server column being there.

Darren

"Erland Sommarskog" <som...@algonet.se> wrote in message
news:Xns92BD5F53...@127.0.0.1...

0 new messages