do I need to pay for support cases to help MS fix bugs?

I've filed a few bugs on connect.microsoft.com, and I am being asked for 2nd time to open a support case to make it easier to work on the bug.

The reason is that the bug needs to be reproduced, and working with a support person will help MS setup the same database, cube, etc.

However, I am wondering why am I as a customer required to pay for the support incidents to help Microsoft fix software bugs?

In my view that type of practice might serve as a deterrent for bug filing and follow-ups. I am sure this is not the desired effect.

I have filed many bugs on connect without any demands of opening a support case.

The response is usually rapid if you participate in beta testing of service packs.

Probably you pay for a quick delivery of hot-fixes.

HTH

Thomas Ivarsson

|||

No, you pay only if you support case wasn't MS error.

If you file an issue that is a bug, you pay nothing. For the hotfix you pay nothing. But the way from bug support case to the hotfix is some time long and difficult.

Divide by Zero error

With the following sql I get a divide by zero error. Can somebody help me
with the syntax to fix this?
Thanks in advance
SUM(CASE WHEN (p.SecondaryCapacity/p.SecondaryWatts) < (m.SecondaryEERSpec -
(-1 * (@.LowerSpec * m.SecondaryEERSpec))) OR
(p.SecondaryCapacity/p.SecondaryWatts) > (m.SecondaryEERSpec +
(@.UpperSpec * m.SecondaryEERSpec)) THEN 1 Else 0 END) as SecondaryEERFailure
sHow about checking for p.SecondaryWatts first?
SUM(
CASE WHEN (p.SecondaryWatts =0) THEN -1
WHEN (p.SecondaryCapacity/p.SecondaryWatts) <
(m.SecondaryEERSpec - (-1 * (@.LowerSpec * m.SecondaryEERSpec)))
OR
(p.SecondaryCapacity/p.SecondaryWatts) > (m.SecondaryEERSpec +
(@.UpperSpec * m.SecondaryEERSpec))
THEN 1 Else 0 END
) as SecondaryEERFailures
"StvJston" wrote:

> With the following sql I get a divide by zero error. Can somebody help me
> with the syntax to fix this?
>
> Thanks in advance
> SUM(CASE WHEN (p.SecondaryCapacity/p.SecondaryWatts) < (m.SecondaryEERSpec
-
> (-1 * (@.LowerSpec * m.SecondaryEERSpec))) OR
> (p.SecondaryCapacity/p.SecondaryWatts) > (m.SecondaryEERSpec +
> (@.UpperSpec * m.SecondaryEERSpec)) THEN 1 Else 0 END) as SecondaryEERFailu
res
>|||Kevin,
Thanks for your reply. I just got it figured out and did just what you
suggested.
SUM(CASE WHEN p.SecondayWatts = 0 THEN 0
ELSE CASE WHEN (p.SecondaryCapacity/p.SecondaryWatts) <
(m.SecondaryEERSpec - (-1 * (@.LowerSpec * m.SecondaryEERSpec))) OR
(p.SecondaryCapacity/p.SecondaryWatts) > (m.SecondaryEERSpec +
(@.UpperSpec * m.SecondaryEERSpec)) THEN 1 Else 0 END END) as
SecondaryEERFailures,
"Kevin Bowker" wrote:
> How about checking for p.SecondaryWatts first?
> SUM(
> CASE WHEN (p.SecondaryWatts =0) THEN -1
> WHEN (p.SecondaryCapacity/p.SecondaryWatts) <
> (m.SecondaryEERSpec - (-1 * (@.LowerSpec * m.SecondaryEERSpec)))
> OR
> (p.SecondaryCapacity/p.SecondaryWatts) > (m.SecondaryEERSpec +
> (@.UpperSpec * m.SecondaryEERSpec))
> THEN 1 Else 0 END
> ) as SecondaryEERFailures
> "StvJston" wrote:
>

Distribution Subsystem: agent (null) failed.

Win 2k & SQL 2k SP3a
This error appears in my Application Log. How can I fix/remove/delete
this? How can I determine what dB this is from?
~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
Event Type:Error
Event Source:MSSQLSERVER
Event Category:(2)
Event ID:17052
Date:12/23/2005
Time:8:00:11 AM
User:ROUSES.COM\Administrator
Computer:ROUSEONE
Description:
Error: 14151, Severity: 18, State: 1
Replication-Replication Distribution Subsystem: agent (null) failed.
The subscription to publication '(null)' has expired and does not
exist.
Data:
0000: 47 37 00 00 12 00 00 00 G7.....
0008: 09 00 00 00 52 00 4f 00 ...R.O.
0010: 55 00 53 00 45 00 4f 00 U.S.E.O.
0018: 4e 00 45 00 00 00 0d 00 N.E....
0020: 00 00 64 00 69 00 73 00 ..d.i.s.
0028: 74 00 72 00 69 00 62 00 t.r.i.b.
0030: 75 00 74 00 69 00 6f 00 u.t.i.o.
0038: 6e 00 00 00 n...
Run your agents one by one to see if you can manually force this error in
your event log.
Hilary Cotter
Looking for a SQL Server replication book?
http://www.nwsu.com/0974973602.html
Looking for a FAQ on Indexing Services/SQL FTS
http://www.indexserverfaq.com
"LPR-3rd" <lreames@.gmail.com> wrote in message
news:1135354198.113526.29560@.z14g2000cwz.googlegro ups.com...
> Win 2k & SQL 2k SP3a
> This error appears in my Application Log. How can I fix/remove/delete
> this? How can I determine what dB this is from?
> ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~
>
> Event Type: Error
> Event Source: MSSQLSERVER
> Event Category: (2)
> Event ID: 17052
> Date: 12/23/2005
> Time: 8:00:11 AM
> User: ROUSES.COM\Administrator
> Computer: ROUSEONE
> Description:
> Error: 14151, Severity: 18, State: 1
> Replication-Replication Distribution Subsystem: agent (null) failed.
> The subscription to publication '(null)' has expired and does not
> exist.
> Data:
> 0000: 47 37 00 00 12 00 00 00 G7.....
> 0008: 09 00 00 00 52 00 4f 00 ...R.O.
> 0010: 55 00 53 00 45 00 4f 00 U.S.E.O.
> 0018: 4e 00 45 00 00 00 0d 00 N.E....
> 0020: 00 00 64 00 69 00 73 00 ..d.i.s.
> 0028: 74 00 72 00 69 00 62 00 t.r.i.b.
> 0030: 75 00 74 00 69 00 6f 00 u.t.i.o.
> 0038: 6e 00 00 00 n...
>

Distribution Agent Error

What does...Error at parameter 12 during datastream processing of
parameterized command...mean? How do I fix it?
Larry...
Basically it means that when the log reader was construction the
parameterized statements to build your proc which it uses to apply the
transaction on the subscriber, it encountered an error with the 12th
parameter.
You can encounter these errors when you are doing funky stuff with custom
sync objects, views, horizontal or vertical partitioning.
I have also seen problems when you update a text field with a null or
perhaps a ''.
"Larry" <Larry@.discussions.microsoft.com> wrote in message
news:A74D6C65-2E5A-4DA5-9840-3035E23A82DA@.microsoft.com...
> What does...Error at parameter 12 during datastream processing of
> parameterized command...mean? How do I fix it?
> Larry...
|||So how do I fix it? How do I recover the lost transaction?