[Qt-interest] x64 Driver for SQL Server

[Scott Aron Bloom]

Make sure all your select queries are using 'with (nolock)'

 

Scott

 

From: qt-interest-bounces at trolltech.com
[mailto:qt-interest-bounces at trolltech.com] On Behalf Of Bill Moo
Sent: Thursday, June 24, 2010 1:15 AM
To: Tony Rietwyk
Cc: qt-interest at trolltech.com
Subject: Re: [Qt-interest] x64 Driver for SQL Server

 

 

On Thu, Jun 24, 2010 at 8:40 AM, Tony Rietwyk
<tony.rietwyk at rightsoft.com.au> wrote:

Hi Bill, 

 

What is the connection error returned when it fails?  

 

Do you have enough concurrent licences for the number threads accessing
the database?  

 

Tony.

 

 

 


I've just been sent this from testing and not quite the connection error
I was expecting!

QODBCResult::exec: Unable to execute statement: "  [Microsoft][SQL
Native Client][SQL Server]Transaction (Process ID 59) was deadlocked on
lock resources with another process and has been chosen as the deadlock
victim. Rerun the transaction." 

"  [Microsoft][SQL Native Client][SQL Server]Transaction (Process ID 59)
was deadlocked on lock resources with another process and has been
chosen as the deadlock victim. Rerun the transaction. QODBC3: Unable to
execute statement"

The text above is repeated four times (once for each of the INSERTions)
and when this appears in the log files access to SQL server is blocked
even from the likes of SQL Studio, and this error only appears after the
other MDI windows have crashed as a result of the connection issue, and
demands a SQL restart to 'fix' it.

A description of the the original connection error I cannot provide at
the moment but have requested.

As regards concurrency this shouldn't be an issue as the Server is
licenced using Processor Licences.

-- 
Bill



-------------- next part --------------
An HTML attachment was scrubbed...
URL: http://lists.qt-project.org/pipermail/qt-interest-old/attachments/20100624/c03e3219/attachment.html