I can give a partial answer regarding the statutes and ordinances - in Hebrew "Chukim Umishpatim"

A statute is a law that has no "logical" reasoning for example, the laws of kashrut (kosher) are not based on human "logic". We cannot logically reason why we cannot eat shellfish, for example.

An oridnance - "mishpat" is something that we can logically determine. We intrinsically know that we shouldn't steal, because civilized people understand the protection of other people's property and it is "immoral" to steal.

Regardless of the classification of the law, we should perform them with the intention that God commanded us to do them, even if it's something we would think of doing on our own.

What is the difference between the following words referring to commandments?
We had to restart our SQL Server today, we had made no changes to it.

When it came back up we immediately started getting this error from the server


  DATE/TIME:    2/27/2014 3:09:31 PM
  
  DESCRIPTION:  The SQL Server performance counter 'Number of
  Deadlocks/sec' (instance 'Database') of object 'SQLServer:Locks' is
  now above the threshold of 1.00 (the current value is 2.00).
  
  COMMENT:  (None)
  
  JOB RUN:  (None)


We ran the DBCC TRACEON (1204) command and have watched the log's but it's not reporting any deadlocks.

Any idea what could trigger this to just go off? We are getting the alert every minute yet can't find any actual deadlocks.

Edit: I should add that before this reboot we had never received this error

Edit 2: We used SQL Server Profiler as well to look for deadlocks, let it run for 5 minutes over which we received 5 error alerts and when we checked the details we had NO deadlocks found.

Edit 3: March 06/2014: Ran the query and it worked, but it reports what our other details have said that we have no locks we where still getting the error above the whole time.

Thanks again for all your help!



Edit 4: March 06/2014: I ran the query and here is a sampling of the result set, I will admit I am not exactly sure what I am looking at here, that is to say I am not sure if it shows me something that I can act on or not.



Edit 5: March 07/2014: Image below shows the Alert that generates this error all of a sudden.



Thanks
