• To add onto Luis's suggestion:

    WITH SampleData AS (

    SELECT test = 'my email is Test@email.com.au how do i capture just the email' UNION ALL

    SELECT 'Some invalid@email addresses can also be removed like this' UNION ALL

    SELECT 'Some invalid @email addresses can also be removed like this' UNION ALL

    SELECT 'Some invalid email@. addresses can also be removed like this' UNION ALL

    SELECT 'Some invalid email@@address.can can also be removed like this' UNION ALL

    SELECT 'No email address in this string'

    )

    SELECT test, item

    FROM SampleData a

    CROSS APPLY dbo.DelimitedSplit8K(test, ' ') b

    WHERE CHARINDEX('@', item) < CHARINDEX('.', item) AND CHARINDEX('@', item) > 1 AND

    CHARINDEX('.', item) < LEN(item) AND LEN(item) - 1 = LEN(REPLACE(item, '@', ''));

    Etc.


    My mantra: No loops! No CURSORs! No RBAR! Hoo-uh![/I]

    My thought question: Have you ever been told that your query runs too fast?

    My advice:
    INDEXing a poor-performing query is like putting sugar on cat food. Yeah, it probably tastes better but are you sure you want to eat it?
    The path of least resistance can be a slippery slope. Take care that fixing your fixes of fixes doesn't snowball and end up costing you more than fixing the root cause would have in the first place.

    Need to UNPIVOT? Why not CROSS APPLY VALUES instead?[/url]
    Since random numbers are too important to be left to chance, let's generate some![/url]
    Learn to understand recursive CTEs by example.[/url]
    [url url=http://www.sqlservercentral.com/articles/St