Sql target table lock when used in SQL procedure and informatica workflows

Question

1.00/5 (1 vote)

See more:

Hi,

My question is regarding concurrency and locking mechanism.

In my project, Informatica and SQL procedures have to process on a single SQL table.
Process 1:
Informatica dumps a set of records into SQL table X.
Then SQL procedure need to take that set from X to process and then dump the result into X again.
Process 2: same with other set of records.
there are such 14 or more processes.

In such case, locking will be an issue on table X.
Please suggest how to minimize the risk of locking so that no process will stop working due to lock on X.

What I have tried:

I want to know the suggestions and mechanisms which can be used to avoid locking the target table.

Posted 20-Dec-17 23:03pm

Tamanna Sharma

Updated 8-Jan-18 20:14pm

Add a Solution

1 solution

Add a Solution

Add your solution here

Treat my content as plain text, not as HTML

Preview 0

…

Existing Members

Sign in to your account

...or Join us

Download, Vote, Comment, Publish.

Your Email
Password
Forgot your password?

Your Email
This email is in use. Do you need your password?
Optional Password

I have read and agree to the Terms of Service and Privacy Policy
Please subscribe me to the CodeProject newsletters

When answering a question please:

Read the question carefully.
Understand that English isn't everyone's first language so be lenient of bad spelling and grammar.
If a question is poorly phrased then either ask for clarification, ignore it, or edit the question and fix the problem. Insults are not welcome.
Don't tell someone to read the manual. Chances are they have and don't get it. Provide an answer or move on to the next question.

Let's work to help developers, not make them feel stupid.

This content, along with any associated source code and files, is licensed under The Code Project Open License (CPOL)

Rajesh Pandya · Accepted Answer · 2018-01-08T20:13:00

You can dislable lock escalation. For disalbe lock escalation you can specify at the table level using ALTER TABLE tablename SET(lock_escalation = DISABLE).
For more detail look at https://msdn.microsoft.com/en-us/library/ms190273.aspx

If you disable it can result in higher memory consumption. So before disabling it review it thoroughly.