Apache Pig differs from SQL in its usage for ETL, lazy evaluation, STORE data at any given point of TIME in the pipeline, support for pipeline splits and explicit declaration of execution plans. SQL is oriented around queries which produce a single result. SQL has no in-built mechanism for SPLITTING a data processing stream and applying different OPERATORS to each sub-stream.

Apache Pig allows user code to be included at any point in the pipeline whereas if SQL where to be USED data needs to be imported to the database first and then the process of cleaning and transformation begins.

Apache Pig differs from SQL in its usage for ETL, lazy evaluation, store data at any given point of time in the pipeline, support for pipeline splits and explicit declaration of execution plans. SQL is oriented around queries which produce a single result. SQL has no in-built mechanism for splitting a data processing stream and applying different operators to each sub-stream.

Apache Pig allows user code to be included at any point in the pipeline whereas if SQL where to be used data needs to be imported to the database first and then the process of cleaning and transformation begins.