Share
ReportHi All,
I am looking for help in determining why the load is so slow.
Even though it is a complete refresh, shouldn't it run more quickly?
I have followed documentation to setup a couple target entities (customerAddress, Customer, CustGroup)
CustGroup went accross - even to the Data Store Db , but Customer is queued up behind CustAddress
The Entity Store Db is on an Azure instance with connection as ODBC 64 bit, but the problem is that loading
of the staging table has been running for over 24 hours and only about half of the 4 million rows have made it to staging.
At this rate, a complete refresh would take forever. Here is the Target entity row.
Running SP_whoisActive returns the following. The query is below that is running..
| CPU | tempdb_allocations | tempdb_current | blocking_session_id | reads | writes | physical_reads | used_memory | status | open_tran_count | percent_complete | host_name |
| 65,969,342 | 0 | 0 | NULL | 123,650,557,912 | 293,475 | 35,055 | 12 | runnable | 1 | NULL | AX-DEV |
SELECT T1.ENTITY,T1.ENTITYFIELD,T1.MAPPINGTYPE,T1.METHODDATASOURCE,T1.METHODNAME,T1.METHODRETURNPOSITION,T1.POSITION,
T1.RUNMODIFIEDFIELD,T1.RUNVALIDATEFIELD,T1.XMLFIELD,T1.RECVERSION,T1.PARTITION,T1.RECID,T2.ENTITY,T2.ISAUTOMANUAL,
T2.TARGETDATASOURCENAME,T2.TARGETFIELD,T2.TARGETTABLE,T2.XMLFIELD,T2.RECVERSION,T2.PARTITION,T2.RECID
FROM DMFTARGETXMLTOENTITYMAP T1
LEFT OUTER JOIN DMFTARGETXML T2 ON ((T2.PARTITION=@P1)
AND (((T1.ENTITY=T2.ENTITY)
AND (T1.XMLFIELD=T2.XMLFIELD))
AND (T2.TARGETDATASOURCENAME=@P2)))
WHERE ((T1.PARTITION=@P3) AND (T1.ENTITY=@P4)) ORDER BY T1.POSITION
Any things I can check, or any suggestions are welcome. Thanks!
*This post is locked for comments
All responses (
Answers (
291,280
