Checking for database concurrency violations

[msx23]

In the app I'm writing I would like to be able to check if any concurrency violations have occurred on the database it's monitoring in the recent past. In SQL Server Management studio I can run the command DBCC CONCURRENCYVIOLATION which gives me the message back (where I forced concurrency violations): Concurrency violations since 2007-10-10 10:47:47.383 1 2 3 4 5 6 7 8 9 10-100 >100 4727 2800 1118 0 0 0 0 0 0 0 0 Concurrency violations will be written to the SQL Server error log. DBCC execution completed. If DBCC printed error messages, contact your system administrator. So this is the info I need, the way that I'm trying to get it into my program is: conn.Open(); conn.InfoMessage += new SqlInfoMessageEventHandler(SqlMessageEventHandler); SqlCommand c = new SqlCommand("DBCC CONCURRENCYVIOLATION", conn); c.ExecuteNonQuery(); where conn is my SQL connection and SqlMessageEventHandler grabs the error message: public void SqlMessageEventHandler(object sender, SqlInfoMessageEventArgs e) { string CVTest = ""; foreach (SqlError err in e.Errors) { CVTest += err.Message; } } The problem is that the "CVTest" sting I'm using to monitor the message only gives me back DBCC execution completed. If DBCC printed error messages, contact your system administrator.rather than the whole message as in Server Management Studio. This occurs whether the DB I'm checking has violations logged or not. Does anyone know how I can get all the information that DBCC CONCURRENCYVIOLATION should return? Alternatively, if anyone knows a better way to programatically check for concurrency violations that have occurred on the database that would be great, since parsing that message to determine can't be the most efficient way. Thank you.

[Robert Rohde]

I might be wrong but have you looked at what is inside the Message property of the SqlInfoMessageEventArgs in your case:

public void SqlMessageEventHandler(object sender, SqlInfoMessageEventArgs e)
{
string CVTest = e.Message;
foreach (SqlError err in e.Errors)
CVTest += Environment.NewLine + err.Message;
}

Robert

[msx23]

Hey, thanks for the reply. Yeah, the Message property only contains that one line response as well instead of the whole message. Anyone have any other ideas on how to check for concurrency violations? Thanks