|
|
Posted by Erland Sommarskog on 11/05/05 00:47
dubing@gmail.com (dubing@gmail.com) writes:
> In that page you summarized various connectivity solutions, seems you
> had some concerns with FreeTDS by saying:
>
> "but personally I would be very wary of using something like this in
> business-critical code".
>
> What's the story behind that? FreeTDS is completely new to me. I'd
> appreciate any suggestions or warnings so I can have something to keep
> in mind while I'm look further.
I have no experience of FreeTDS. But since FreeTDS is the reverse-
engineering of a proprietary protocol you are taking things on a dare.
There may be errors or oversights in the reverse-engineering. Most
likely such errors leads to crashes somewhere, but if things go really
bad, it results in incorrect data being read from/written to the database.
There is also the issue what happens if you open a case with Microsoft.
I have to idea what they say if you say that you connect with FreeTDS,
but it's clearly not a supported means of connection. It could be that
the issue you have run into is a bug in MS SQL Server, but since you
connect with FreeTDS, Microsoft may not look into the issue. (As they
may assume that FreeTDS is the culprit.)
--
Erland Sommarskog, SQL Server MVP, esquel@sommarskog.se
Books Online for SQL Server SP3 at
http://www.microsoft.com/sql/techinfo/productdoc/2000/books.asp
Navigation:
[Reply to this message]
|