FreeTDS Development Group

["Thompson, Bill D (London)" <bill.d.thompson AT baml.com>]

James,

you were, of course, correct!
although, alas, I lack the big office, comfy couch and secretary you
allude to, I was able find some time to adjuust the grade of my
toothcomb and engage in the hard slog of going through a few thousand
lines of stored procedure code.
and there it was...

Your sound advice was, as ever, invaluable :-)

Bill

-----Original Message-----
From: freetds-bounces AT lists.ibiblio.org
[mailto:freetds-bounces AT lists.ibiblio.org] On Behalf Of
jklowden AT schemamania.org
Sent: 05 October 2010 18:46
To: FreeTDS Development Group
Subject: Re: [freetds] An *old* issue I need some help with


On Tue, Oct 05, 2010 at 04:52:49PM +0100, Thompson, Bill D (London)
wrote:
> Hey James,
> 
> > Looks like your complicated proc is selecting a nullable FLOAT
> somewhere.  
> 
> I'm pretty sure not...I have an accompanying SQL Profiler trace which
> I've been through with a fine tooth comb.

I tested it on 2000 and 2005 and didn't get the D1 token, but that's not
to say there's not an option that would generate one.  I still think
it's a SELECT statement or an explicit OUTPUT.  I know, even though
you've looked.  

> 
> I think something this is more likely....a number of posts seem to
point
> to something funny going on - for example:

Nah.  Those questions are all from people confused by how client
libraries treat severity 16 messages from the server.  It seems 2008
uses severity 16 for msg 3604; my servers and yours show severity 0:  

http://msdn.microsoft.com/en-us/library/ms188783.aspx

(If it were up to me, IGNORE_DUP_KEY would be a syntax error.)  

The only thing you have in commmon with them is -- begging your pardon,
sir! -- bad design.  If I were you, in your big office with your comfy
couch, I'd have the secretary fetch me some coffee and use the time to
impose a proper key and write a proper query!  Gets the right answer and
beats snooping with a profiler any day.  

But, of course, if you can't do that and you do manage to shed some
light in this dark corner, I'd be very interested to hear what you
discover.  

Sorry not to be more helpful.  Perhaps someone else knows....

Regards, 

--jkl
_______________________________________________
FreeTDS mailing list
FreeTDS AT lists.ibiblio.org
http://lists.ibiblio.org/mailman/listinfo/freetds

----------------------------------------------------------------------
This message w/attachments (message) is intended solely for the use of the 
intended recipient(s) and may contain information that is privileged, 
confidential or proprietary. If you are not an intended recipient, please 
notify the sender, and then please delete and destroy all copies and 
attachments, and be advised that any review or dissemination of, or the 
taking of any action in reliance on, the information contained in or attached 
to this message is prohibited. 
Unless specifically indicated, this message is not an offer to sell or a 
solicitation of any investment products or other financial product or 
service, an official confirmation of any transaction, or an official 
statement of Sender. Subject to applicable law, Sender may intercept, 
monitor, review and retain e-communications (EC) traveling through its 
networks/systems and may produce any such EC to regulators, law enforcement, 
in litigation and as required by law. 
The laws of the country of each sender/recipient may impact the handling of 
EC, and EC may be archived, supervised and produced in countries other than 
the country in which you are located. This message cannot be guaranteed to be 
secure or free of errors or viruses. 

References to "Sender" are references to any subsidiary of Bank of America 
Corporation. Securities and Insurance Products: * Are Not FDIC Insured * Are 
Not Bank Guaranteed * May Lose Value * Are Not a Bank Deposit * Are Not a 
Condition to Any Banking Service or Activity * Are Not Insured by Any Federal 
Government Agency. Attachments that are part of this EC may have additional 
important disclosures and disclaimers, which you should read. This message is 
subject to terms available at the following link: 
http://www.bankofamerica.com/emaildisclaimer. By messaging with Sender you 
consent to the foregoing.