Contents
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.
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.
Do you need to create previous week filter?
As in, do you need to be able to look at records that were entered only in the week previous to -right now-, or do you need to be able to look at a range of dates, and say “Well, the week of Jan 7,2007 had X Bookings, and the previous week had Y Bookings”?
How to create a previous week filter in Power BI?
If you only need to analyze the week leading up to right now, this point in time, just modify your query to only pull records with dates that are after NOW () -7. If you need the latter, we need a bit more information about your data model.
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.
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.