Showing posts with label events. Show all posts
Showing posts with label events. Show all posts

Tuesday, March 27, 2012

duplicate RPC:Completed events in trace file

Has anyone ever seen duplicate RPC:Completed events in a trace file?
I've got several rows in which the colum values are the exact same. I
was guessing this might be parallel execution, but its just a guess...
thx,
--oj.Hi
I have not seen duplicated events. What version of SQL Server are you using?
What columns/filters are using? Are you logging to screen/file or table?
John
"seraph" wrote:

> Has anyone ever seen duplicate RPC:Completed events in a trace file?
> I've got several rows in which the colum values are the exact same. I
> was guessing this might be parallel execution, but its just a guess...
> thx,
> --oj.
>

duplicate RPC:Completed events in trace file

Has anyone ever seen duplicate RPC:Completed events in a trace file?
I've got several rows in which the colum values are the exact same. I
was guessing this might be parallel execution, but its just a guess...
thx,
--oj.
Hi
I have not seen duplicated events. What version of SQL Server are you using?
What columns/filters are using? Are you logging to screen/file or table?
John
"seraph" wrote:

> Has anyone ever seen duplicate RPC:Completed events in a trace file?
> I've got several rows in which the colum values are the exact same. I
> was guessing this might be parallel execution, but its just a guess...
> thx,
> --oj.
>

duplicate RPC:Completed events in trace file

Has anyone ever seen duplicate RPC:Completed events in a trace file?
I've got several rows in which the colum values are the exact same. I
was guessing this might be parallel execution, but its just a guess...
thx,
--oj.Hi
I have not seen duplicated events. What version of SQL Server are you using?
What columns/filters are using? Are you logging to screen/file or table?
John
"seraph" wrote:
> Has anyone ever seen duplicate RPC:Completed events in a trace file?
> I've got several rows in which the colum values are the exact same. I
> was guessing this might be parallel execution, but its just a guess...
> thx,
> --oj.
>

Thursday, March 22, 2012

Duplicate Events

The nature of the event provider for my SQLNS application is to produce
exact duplicate rows into the event table. Obviously, I am not
interested in receiving duplicate notifications. What are some
strategies for having SQLNS produce one notification for several exact
rows being sent to the events table.

I have an event chronicle that retrieves distinct rows from the event
table and puts them into the chronicle. My thoughts were that I could
use the chronicle table in my matching statement. But the timing
doesn't seem to be working out. The matching is apparently done before
the chronicle is updated.

Any thoughts on strategies for having SQLNS produce one notification
for several exact rows being sent to the events table.

There is probably a more direct method to accomplish your goals. I'd suggest you really consider filtering the duplicate events in the event provider before they ever get to the events table.

However, if that's the route you want to take, the matching rule is
really just a T-SQL statement. Version 2.0 uses a UDF to create the
resultset while v2005 uses a new view to do the same. So you can try using a combination of the chronicle table with the distinct keyword to filter out the dups.

BTW - matching rules are processed in the following order:
- Event chronicle rules
- Subscription event rules
- Subscription scheduled rules

HTH...


--
Joe Webb
SQL Server MVP
http://www.sqlns.com


~~~
Get up to speed quickly with SQLNS
http://www.amazon.com/exec/obidos/tg/detail/-/0972688811

I support PASS, the Professional Association for SQL Server.
(www.sqlpass.org)

Duplicate Events

The nature of the event provider for my SQLNS application is to produce
exact duplicate rows into the event table. Obviously, I am not
interested in receiving duplicate notifications. What are some
strategies for having SQLNS produce one notification for several exact
rows being sent to the events table.

I have an event chronicle that retrieves distinct rows from the event
table and puts them into the chronicle. My thoughts were that I could
use the chronicle table in my matching statement. But the timing
doesn't seem to be working out. The matching is apparently done before
the chronicle is updated.

Any thoughts on strategies for having SQLNS produce one notification
for several exact rows being sent to the events table.

There is probably a more direct method to accomplish your goals. I'd suggest you really consider filtering the duplicate events in the event provider before they ever get to the events table.

However, if that's the route you want to take, the matching rule is
really just a T-SQL statement. Version 2.0 uses a UDF to create the
resultset while v2005 uses a new view to do the same. So you can try using a combination of the chronicle table with the distinct keyword to filter out the dups.

BTW - matching rules are processed in the following order:
- Event chronicle rules
- Subscription event rules
- Subscription scheduled rules

HTH...


--
Joe Webb
SQL Server MVP
http://www.sqlns.com


~~~
Get up to speed quickly with SQLNS
http://www.amazon.com/exec/obidos/tg/detail/-/0972688811

I support PASS, the Professional Association for SQL Server.
(www.sqlpass.org)