Well, I suppose you're talking mostly about the Profiler classes, but the explanation stands anyway.
An SQL batch is a set of one or more statements grouped together and separated by a GO statement. EG: more SELECT and INSERT statements form a batch if they have a GO at the end.
A RPC call is a call that comes from a client application to the database. EG: a windows service, a web application, a windows app, whatever needs a connection to the database actually makes a RPC call.
Now, in Profiler you'll see everything that touches the database server.
A batch from Management Studio, an RPC call (which is either a batch or a stored procedure call) from an external application, a procedure execution from Management Studio.
Each of them is formed of TSQL statements, so this Profiler class is useful in case you want to expand the execution further, to see what's actually executed. What inserts, selects..etc.
The easiest way to look at them in Profiler is to enable only End RPC call, or End batch call and you'll see there all the statistics needed (duration, IO, CPU). Then, move further by enabling TSQL Statements class and dig deeper.
The execution result, in your case, success, completion, or failure is a precedence link that can create a relationship between two tasks. From BOL
A precedence link between two tasks establishes a relationship between the tasks. The second task (the dependent task) executes only if the execution result of the first task (the precedent task) matches specified criteria. Typically the execution result specified is Success, Failure, or Completion
If you wanted to say, have your plan execute a statement that was not designed around success or failure you could use completion to establish a relationship and proceed to the next task.
Example: Purge all records of type 'A' from database [ABC], then execute a database backup
- You don't care how many records, if any, were found or deleted. Just run the statement. When it is done, back up the database
Example: Reorganize the index's of database [ABC] only after successfully checking the integrity. If the integrity check fails, do not reorganize the index's
Maint. Plans
Precedence Constraints
Best Answer
As per the comments, you are referring to the columns in
sys.databasesAs per SQL Server Docs