Timeline for ERROR: Query failed: Timeout SFMC
Current License: CC BY-SA 4.0
6 events
| when toggle format | what | by | license | comment | |
|---|---|---|---|---|---|
| Apr 3, 2020 at 1:10 | answer | added | Macca | timeline score: 2 | |
| Apr 3, 2020 at 0:56 | comment | added | Macca | Consider the Primary Keys on your staging DE's. You can force the creation of indexes to help with performance. | |
| Apr 3, 2020 at 0:51 | comment | added | Macca | Try breaking your query down into multiple less expensive queries. For example, dump your contacts with assets into a staging table, then try doing your expensive STUFF and XML PATH operation in separate queries using smaller subsets of data. | |
| Apr 3, 2020 at 0:51 | comment | added | Macca | The timeout error's fairly self-explanatory. You're running a very expensive query and it's resulting in a timeout after 30 mins. You'd need to do some tuning. If you're not wanting to know about products with no asset or assets with no contact, why do an outer join? If you don't need Account_Salesforce fields in your output, why join to it? You have the account Id already available in your Contact_Salesforce data. If you're grouping by ContactID and AssetId, what's the point of using a DISTINCT? | |
| Apr 3, 2020 at 0:25 | review | First posts | |||
| Apr 3, 2020 at 6:08 | |||||
| Apr 3, 2020 at 0:24 | history | asked | JGB | CC BY-SA 4.0 |