title: pyodbc and insert statements
body: <p>I'm using pyodbc quite short period of time and now faced with the problem of applying sql script from file which performs some view creation. For applying sql file I use sample from another thread - <a href="https://stackoverflow.com/questions/10387892/follow-up-execute-sql-files-from-python">Follow up: Execute .sql files from python</a>   Have no problems with majority of my sql scripts but this one causes a problem:</p>
  
  <p>part of script: </p>
  
  <pre><code>insert into TMP_VIEWS select * from TMP_QUERY_SQL
  go
  begin
  declare @SQL_CMD varchar(4000);
  declare @CNT int;
  set @CNT = (select count(1) from TMP_VIEWS);
  while @CNT &gt; 0
  begin 
    set @SQL_CMD = (select top 1 SQL_CMD from TMP_VIEWS order by SQL_CMD);
    print 'Executing: ' + @SQL_CMD;
    EXEC(@SQL_CMD)
    delete from TMP_VIEWS where @SQL_CMD = SQL_CMD;
    set @CNT = (select count(1) from TMP_VIEWS);
  end
  end
  </code></pre>
  
  <p>As you see it performs execution of SQL statements that were inserted to table from another table. So in the way I apply it it doesn't work. Sample from another thread devides sql file into blocks between GO and applyes them. So 'insert into TMP_VIEWS select * from TMP_QUERY_SQL' applied separately and then other part. It looks like pyodbc or driver doesn't actually wait for full execution of insert on server and second block is executed before actuall insert is comlete. As a result I have quite random amount of views created and non-creted queries remained in TMP_VIEWS. I have autocommit and tried to add additional commits after query execution - this doesn't help. The only thing that helps - add time.sleep(0.2) beetween execution of this batches between GO. Looks like some asynchronuous call. Who faces with the same problem or what may be wrong in my attempt? May be some workaround?</p>
  
  <p>Thanks!</p>