subhashkmsbi - Read my post (the one just above yours).

I don't think "R" is an "enemy" if it's going to be included as a new feature in SQL Server 2016.

govind.sharma1:

I think you need to textually parse your XML from the source - an "old school" trick.

Use BULK INSERT to read it like a text file and split it up...

I realize that, by now, there is a consensus that the limit is imposed by LDAP and not OPENQUERY.

However, in a previous job experience I was asked to get around...

I wonder if there is much benefit to using BOTH concurrency AND insert/update. As in "multiple concurrent inserts and updates". Then SQL Server could thread each UPDATE separately....

Where is the MDX query?

If you can identify an XML tag immediately under the root that is repeated for each major section of the text data, then you can bulk import the data with...