PROC SQL is SAS implementation of the query language.
And yes, SAS itself does not support transactions.
If your data is stored in a RDBMS PROC SQL can make use of som transactional behaviour in the database.
Transactions is mainly useful in OLTP scenarios.
What is your requirement/use case regarding this
PROC SQL is SAS implementation of the query language.
And yes, SAS itself does not support transactions.
If your data is stored in a RDBMS PROC SQL can make use of som transactional behaviour in the database.
Transactions is mainly useful in OLTP scenarios.
What is your requirement/use case regarding this
Thanks @LinusH
I was actually trying to explore using transaction to commit changes to a table.
By transactions I mean either all or none are committed or written to the table.
Thanks for answering my question.
@esbabu wrote:
Thanks @LinusH
I was actually trying to explore using transaction to commit changes to a table.
By transactions I mean either all or none are committed or written to the table.
Thanks for answering my question.
A normal data step meets your definition of transactions, the output dataset is only replaced when the data step complete without errors.
For example you might want to use the UPDATE statement to apply transactions to an existing dataset. Note that it does not work in the new CAS environment, only the traditional SAS data step.
It's finally time to hack! Remember to visit the SAS Hacker's Hub regularly for news and updates.
Learn how use the CAT functions in SAS to join values from multiple variables into a single value.
Find more tutorials on the SAS Users YouTube channel.
Ready to level-up your skills? Choose your own adventure.