[Qt-interest] x64 Driver for SQL Server
Bill Moo
cppsysdev at gmail.com
Thu Jun 24 09:27:32 CEST 2010
On Wed, Jun 23, 2010 at 9:22 PM, Constantin Makshin <cmakshin at gmail.com>wrote:
> Could you give more information regarding unreliability of the QODBC
> driver? One of my applications uses it (the application works with data
> generated and used by a 3rd-party program, so there was no choice :) ) and
> it'd be nice to know what problems may arise.
>
> On Wednesday 23 June 2010 15:56:53 Bill Moo wrote:
> > Hi List,
> >
> > Having got no reply to my original post regarding the building of a 64
> bit
> > QTDS SQL Driver I'd would like to ask if I'm wasting my time with this?
> This
> > being an x64 build of a driver that I am able to use for SQL Server. I
> know
> > there is ODBC which I am currently using but it's so unreliable it needs
> to
> > be replaced. I really would appreciate your comments on this one.
>
>
Hi,
Well we have experienced connectivity issues, with the application not being
able to connect and timing out within seconds of another connection
succeeding. We have of course increased the timeout but to no avail. The
application is an MDI with each of the windows using its own unique named
connection, and of course all of these connections using the same ODBC DSN.
I have heard that you can connect to the Server without an ODBC DSN but I'll
be honest and say I don't know how or even if this is correct, but if
someone does know I'd like to hear please.
The weird thing is some of the connections will work for the entire duration
of the application's run time (hours), but others won't. From the initial
SELECT of the data it can be anything from about 2 minutes to 10 minutes
before the database is used again to INSERT the results but can have 'died'
in this time span, but other MDI windows are busy working away!
In addition to this the driver appears to have an 'issue' with the SQL
NOCOUNT ON/OFF in that no rows are returned when NOCOUNT is OFF.
I'm certainly not purporting to be the best C++ programmer in the world, but
stuff like this just winds me up. As the application is MDI then the 'code
base' is identical so why don't all of the SQL connections fail, assuming it
to be badly written code on my side. Needless to say, I have checked the
logic of this but found nothing wrong.
What I really, really can't understand is why a database like SQL Server
doesn't have development support from Nokia, after all it is probably the
most widely used database out there in Windows land and I don't think it's
going to disappear any time soon.
As always any feedback, thoughts would be appreciated.
--
Bill
-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.qt-project.org/pipermail/qt-interest-old/attachments/20100624/2dbd6dec/attachment.html
More information about the Qt-interest-old
mailing list