Using _ for Single Character Matching in SFMC SQL LIKE Operator

🔹 The _ wildcard in SFMC SQL matches exactly ONE character.

Unlike %, which matches multiple characters, _ only replaces a single character.
It’s useful when you need to find values of a fixed format or specific character positions.

`1.` `_` in Fixed-Length Patterns: `_` ensures only one character is replaced at a time.

Since my Source DE did not have two character I used 4 character (Pune: P___)

2. _ in Email Pattern Matching: You can use _ to detect formatting errors in emails.

%@% ensures that "@" appears somewhere in the email.

Question: When I use this filter, it takes all the email address from the source DE so is it not working?

If I use __@gmail.com, it takes only the @gmail.com to target DE but the _ does not define the number of letters before @

`3. _` in Phone Number Validation

'___-___-____' → Ensures that the phone number follows the exact format of 3-3-4 digits.
It excludes numbers that are too short, too long, or missing dashes.

Since the Phone number stored in my Source DE was in format __________ it did not work when i used the format ___-___-____. So the format I use in the Automation filter should match my source DE for it to appear in target DE

Incorrect Format as per my Source DE:

Added with correct Format:

4. `_` in Product Code Matching

'A___' → Matches values that start with "A" followed by exactly three characters.
It excludes A98 (too short) and A1X3 (includes a letter in place of a number).

_ is helpful when product codes follow a fixed structure. (Need to be followed in the same format as source DE. For example if my source DE has a Properties named "ABC DEF", I have to enter the underscore in the same format; '___ ___' and if its ABCDE it should be '_____'. Same number of underscore and same amount of spaces.

Comments

A/B Testing

Confluence link 1: https://elearningit24.atlassian.net/wiki/external/MzA3YWUxNjI3YzBkNGZiZmFlZTc1ZGIzYmU1ZmM1MmQ What is A/B Testing? A/B testing, also known as split testing , is a controlled experiment where two versions of a webpage, email, ad, or any digital asset are tested against each other to determine which one performs better. Why? Higher open rates Better Engagement Increased Sales and Lead conversion Reduced unsubscribed rates Date Driven- No assumption & Proven Results Test Type Subject Line Email Content Area From Name Send Date & Time Pre Header Email Test Template: Friendly and Personalised Straight to the point & Action Oriented Confluence Link 2: https://elearningit24.atlassian.net/wiki/external/NDk0Zjg0ODk3YjAwNDI5ZjkxOTVmMTAxNTQ3ZjlhNmQ Subject Line A/B Test: A/B Testing Use Case: Optimizing Email Subject Lines for Higher Open Rates Scenario- Subject Line: A company wants to increase the open rates of its promotional emails in Sa...

Email Marketing Campaings

Use Cases of Standard Data Extensions 1. Customer Data Storage Scenario : A retail business wants to store customer information, such as names, email addresses, and purchase history, for email marketing campaigns. Solution : Use a standard data extension to store and manage customer data securely and efficiently. Data Extension Structure Field Name Data Type Length Required Primary Key SubscriberKey Text 50 Yes Yes FirstName Text 50 Yes No LastName Text 50 Yes No EmailAddress EmailAddress N/A Yes No PurchaseHistory Decimal N/A No No Sample Records SubscriberKey FirstName LastName EmailAddress PurchaseHistory 001 John Doe john.doe@example.com 1500.50 002 Jane Smith jane.smith@example.com 200.00 https://mc.s8.exacttarget.com/cloud/#app/Email/C12/Default.aspx?entityType=none&entityID=0&ks=ks%23Subscribers

SQl Query

Workflow: Journey Builder> Automation Studio> New Automation Enter Query: Drag and drop Schedule in Start with a Starting Source and the SQL Query> Choose Query> Create New Query Activity> Name your file and add your query (Field name thats part of the DE you create separately- Example: FirstName, LastName, Subscriber Key) Create a new DE in Email Studio with the query field> Select The test DE which was created: Select Target DE and Save & Run Workflow: Select All Activities and Run Workflow: Activity Details: Run Completed with updated DE Edit/ add another query: Copy Source DE and create a new DE with same fields that we are running in SQL: Run the updated SQL Query added Activity and DE updated with Records: Completed Status: Received error: When the Query field and the DE created field does not match When an existing Query is being run, if we try to run another query Fixed the error by matching same field Waiting for existing query to complete

GurbachanBlog

Search This Blog