3 Replies Latest reply: Jan 10, 2013 5:01 PM by Dave Riley RSS

    Script hangs up on OLEDB Connet to SQL Server

      HI,

      My script permenantly hangs around 50% to 75% of the time when trying to connet with a SQL Server Database.

      When debugging with a limited load the script always completes with no issues.

      The test connection always works with no issue. 

      This is becoming very frustrating.

      Is there a setting I need to change?

      Regards,

      Tim

        • Re: Script hangs up on OLEDB Connet to SQL Server
          Dave Riley

          Hi Tim,

           

           

          There's no obvious settings in QV that I can think of. 

           

          Are you querying a database that other users or processes access?  If so, check for Table/Page/Row locks on your database source.

           

          If you are querying a view, maybe convert this into a stored procedure or better still have a process SQL side that creates a table on a schedule that only your QV load process uses.

           

          flipside

            • Re: Script hangs up on OLEDB Connet to SQL Server

              Hi,

              Thank you.

              Is there a way to handle locks from the QlikView script?

               

              Additional information:

              I am noticing that I will kick off a script and the progress does not print to the "Script Execution Progress" Box. Progress does get inserted into the log.

               

              In the cases, where nothing shows in the Script Execution Progress box, then the prgoess stops at the connect statement.

               

              When the Script Execution Progress box does get updated with the progress the OLEDB connect works!

               

              I beleive this could be a memory issue but I have plenty of RAM on my computer...

                • Re: Script hangs up on OLEDB Connet to SQL Server
                  Dave Riley

                  Locks are purely SQL side, they occur when two or more processes try to access the same data at the same time.  They cannot be controlled from QV. You could try using WITH NOLOCK hints on your SQL code.

                   

                  If the script doesn't get past the connect statement I suspect it may be something else anyway - you need to check from the SQL side if the request is being received.

                   

                  flipside