on 2023 Jun 29 10:44 AM
Hey Specs !
We area loading from BW to SQL server 14.0.3421.10 (staging tables) with BODS.
We have been asked to put lock on the target tables (staging tables) to forbid other sessions even from read because on some occasion the target system started to load their staging tables sooner to their propagation layer.
We are loading their staging layer in a very big job it runs 4 hours therefore what would be required is to lock the target table at the begginning of the job, and remove the lock at the end.
My question is there a standard way in BODS to lock the tables included in the job ?
If not is there a non standard way to lock tables if the target system is sql server (used with ODBC connector).
I've tried this method and it is actually working on sql server side, but i am not sure if this is the best approach from bods, especially because if you write a table in the standard way it commits in every 1000 records
locking - SQL Server : lock table to block other sessions trying to read the table - Stack Overflow
Thanks
Hello,
Your question pertains to SAP Data Services, right?
Please use this channel: All Questions in SAP Data Services | SAP Community
Thanks,
Jacob
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
SAP Data Services and SAP Big Data Services are two distinct products in our portfolio:
Each product has a separate community forum. Please use the appropriate forum when submitting your Data Services questions.
Hope this answers your concern.
User | Count |
---|---|
82 | |
12 | |
10 | |
10 | |
10 | |
9 | |
8 | |
7 | |
5 | |
5 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.