Sure.

I created a table, TestData, that contains 1M rows.

IF OBJECT_ID( N'dbo.TestData',N'U' ) IS NOT NULL

DROP TABLE dbo.TestData

GO

CREATE TABLE dbo.TestData (

[RID] UNIQUEIDENTIFIER NOT NULL

, [Group1] VARCHAR ( 8 ) NOT NULL

, [Group2] VARCHAR ( 4 ) NOT NULL

, [Group3] VARCHAR ( 4 ) NOT NULL

, [Group4] VARCHAR ( 4 ) NOT NULL

, [Group5] VARCHAR ( 11 ) NOT NULL

, [DateCreated] DATETIME NOT NULL

, [DateModified] DATETIME NULL

, CONSTRAINT pk_TestData_RID PRIMARY KEY ( RID ASC )

)

GO

Alter Table dbo.TestData

Add Constraint df_TestData_RID DEFAULT ((NewSequentialID())) FOR RID

GO

INSERT dbo.TestData ( Group1, Group2, Group3, Group4, Group5, DateCreated )

SELECT TOP 1000000

(LEFT( CAST( NEWID() AS VARCHAR (36) ), 8 ))

, (SUBSTRING( CAST( NEWID() AS VARCHAR (36) ), 10, 4 ))

, (SUBSTRING( CAST( NEWID() AS VARCHAR (36) ), 15, 4 ))

, (SUBSTRING( CAST( NEWID() AS VARCHAR (36) ), 20, 4 ))

, (SUBSTRING( CAST( NEWID() AS VARCHAR (36) ), 25, 11 ))

, CASE WHEN ASCII( CAST( NEWID() AS VARCHAR (36) ) ) % 2 = 0 THEN

DATEADD( MONTH,ASCII( CAST( NEWID() AS VARCHAR (36) ) ) *-1,GETDATE() )

ELSE

DATEADD( DAY,ASCII( CAST( NEWID() AS VARCHAR (36) ) ) *-1,GETDATE() )

END AS [DateCreated]

FROM sys.objects a CROSS JOIN

sys.tables b CROSS JOIN

sys.partitions c CROSS JOIN

sys.columns d

GO

Create NonClustered Index idx_TestData_DateCreatedDateModified

ON dbo.TestData ( DateCreated, DateModified )

Include ( RID, Group1, Group2, Group3, Group4, Group5 )

GO

UPDATE dbo.TestData

SET DateModified = (DATEADD( millisecond,ASCII( CAST( RID AS VARCHAR (36) ) ),DateCreated ))

GO

Then, I perform my query against the data using the LIKE operator vs. the PATINDEX function.

SELECT *

FROM dbo.TestData

WHERE Group3 LIKE '%4E39%';

GO

SELECT *

FROM dbo.TestData

WHERE PATINDEX('%4E39%',Group3) != 0;

GO

In my testing, the LIKE operator requires parallelism and additional overhead to complete as opposed to the PATINDEX function.