I have a process running in a separate thread which reads data over Ethernet and raises an event for each read. Then, this data is processed over a tree of classes. At the top of my class tree, I want to store the processed data to SQL tables. This read rate can be rather fast and often at times but on average its slower than my write rate to SQL. This is why I want a queue. Also I want my window not to freeze, so I want a separate thread.
The code below works but I'm fairly inexperienced in multi threading. Is this a good and robust way to accomplish my task?
Private addLogQueue As New Queue Private dequeueing As Boolean = False Public Sub addLogHandler(ByVal machineName As String, ByVal LogTime As Date, ByVal EventLog As String, ByVal EventValue As String) addLogQueue.Enqueue("INSERT INTO ... some SQL CODE") Dim Thread1 As New System.Threading.Thread(AddressOf addLog) Thread1.Start End Sub Private Sub addLog() If Not dequeueing Then dequeueing = True While addLogQueue.Count <> 0 Try SQLCon.Open() SQLCmd = New SqlCommand(addLogQueue.Dequeue(), SQLCon) SQLCmd.ExecuteNonQuery() SQLCon.Close() Catch ex As Exception MsgBox(ex.Message) If SQLCon.State = ConnectionState.Open Then SQLCon.Close() End If End Try End While dequeueing = False End If End Sub
After thinking a bit I realize I might not even need a queue or the dequeueing boolean, can I just start a new thread for every write maybe. I added the queue before I added the multi thread because at times I had to write before the SQLcon is even closed. Since I've added a thread, should I even keep the queue?