Contents
Why does SFMC-sprignaturemoves error out after 30 minutes?
If any of your source data extension columns are larger than the target, then you can adjust the length of the target column or use the left () SQL function to trim the value: Probably the most frustrating error is the the 30 minute timeout. If your query won’t run in that amount of time, then it’ll error out.
Do you need to join multiple system data views in SFMC?
While we don’t have any insight in to the indexes that SFMC behind the scenes, it’s a good bet the primary keys are indexes. So the more utilize their values in the where-clause, the better. Don’t join multiple System Data Views in your query.
How to reduce number of rows in SFMC?
First and foremost, you need to reduce the number of row you’re querying. This can be altering your date range or adding additional criteria to target rows more specifically. Leverage the primary keys for speed. While we don’t have any insight in to the indexes that SFMC behind the scenes, it’s a good bet the primary keys are indexes.
Where to find SFMC support in Automation Studio?
SFMC Support can certainly tell you exactly what the error was, and now you can (sometimes) see some error details in the Activity tab of Automation Studio. Here are a few things that I’ve found are common things that cause Query Activities to fail.
How to reduce number of queries in SFMC?
Here are some tips: First and foremost, you need to reduce the number of row you’re querying. This can be altering your date range or adding additional criteria to target rows more specifically. Leverage the primary keys for speed.
What should I do if my SQL query has a 30 minute timeout?
You can utilize the isnull () SQL function to handle that situation: If any of your source data extension columns are larger than the target, then you can adjust the length of the target column or use the left () SQL function to trim the value: Probably the most frustrating error is the the 30 minute timeout.