Try this

Query(For Sql Server):

select * from mytbl
order by SUBSTRING(email,(CHARINDEX( @ ,email)+1),1)

Query(For Oracle):

select * from mytbl
order by substr(email,INSTR(email, @ ,1) + 1,1)

Query(for MySQL)

pygorex1 already answered

Output:

id name email

5   Tarrack Ocama   me@am-no-president.org
3   Ali Baba    ali@babaland.com
1   John Doe    johndoe@domain.com
2   Jane Doe    janedoe@helloworld.com
4   Foo Bar foo@worldof.bar.net

For MySQL:

select email, SUBSTRING_INDEX(email, @ ,-1) AS domain from user order by domain desc;

For case-insensitive:

select user_id, username, email, LOWER(SUBSTRING_INDEX(email, @ ,-1)) AS domain from user order by domain desc;

If you want this solution to scale at all, you should not be trying to extract sub-columns. Per-row functions are notoriously slow as the table gets bigger and bigger.

The right thing to do in this case is to move the cost of extraction from select (where it happens a lot) to insert/update where it happens less (in most normal databases). By incurring the cost only on insert and update, you greatly increase the overall efficiency of the database, since that s the only point in time where you need to do it (i.e., it s the only time when the data changes).

In order to achieve this, split the email address into two distinct columns in the table, email_user and email_domain). Then you can either split it in your application before insertion/update or use a trigger (or pre-computed columns if your DBMS supports it) in the database to do it automatically.

Then you sort on email_domain and, when you want the full email address, you use email_name| @ |email_domain.

Alternatively, you can keep the full email column and use a trigger to duplicate just the domain part in email_domain, then you never need to worry about concatenating the columns to get the full email address.

It s perfectly acceptable to revert from 3NF for performance reasons provided you know what you re doing. In this case, the data in the two columns can t get out of sync simply because the triggers won t allow it. It s a good way to trade disk space (relatively cheap) for performance (we always want more of that).

And, if you re the sort that doesn t like reverting from 3NF at all, the email_name/email_domain solution will fix that.

This is also assuming you just want to handle email addresses of the form a@b - there are other valid email addresses but I can t recall seeing any of them in the wild for years.

For SQL Server, you could add a computed column to your table with extracts the domain into a separate field. If you persist that column into the table, you can use it like any other field and even put an index on it, to speed things up, if you query by domain name a lot:

ALTER TABLE Table1
  ADD DomainName AS 
     SUBSTRING(email, CHARINDEX( @ , email)+1, 500) PERSISTED

So now your table would have an additional column "DomainName" which contains anything after the "@" sign in your e-mail address.

Assuming you really must cater for MySQL, Oracle and MSSQL .. the most efficient way might be to store the account name and domain name in two separate fields. The you can do your ordering:

select id,name,email from table order by name

select id,name,email,account,domain from table order by email

select id,name,email,account,domain from table order by domain,account

as donnie points out, string manipulation functions are non standard .. that is why you will have to keep the data redundant!

I ve added account and domain to the third query, since I seam to recall not all DBMSs will sort a query on a field that isn t in the selected fields.

This will work with Oracle:

select id,name,email,substr(email,instr(email, @ ,1)+1) as domain
from table1
order by domain asc

For postgres the query is:

SELECT * FROM table
ORDER BY SUBSTRING(email,(position( @  in email) + 1),252)

The value 252 is the longest allowed domain (since, the max length of an email is 254 including the local part, the @, and the domain.

See this for more details: What is the maximum length of a valid email address?

You are going to have to use the text manipulation functions to parse out the domain. Then order by the new column.

MySQL, an intelligent combination of right() and instr()

SQL Server, right() and patindex()

Oracle, instr() and substr()

And, as said by someone else, if you have a decent to high record count, wrapping your email field in functions in you where clause will make it so the RDBMS can t use any index you might have on that column. So, you may want to consider creating a computed column which holds the domain.

If you have million records, I suggest you to create new column with domain name only.

My suggestion would be (for mysql):

SELECT 
    LOWER(email) AS email,
    SUBSTRING_INDEX(email,  @ , + 1) AS account,
 REPLACE(SUBSTRING_INDEX(email,  @ , -1), CONCAT( . ,SUBSTRING_INDEX(email,  . , -1)),  ) -- 2nd part of mail - tld.
  AS domain,
    CONCAT( . ,SUBSTRING_INDEX(email,  . , -1)) AS tld
FROM
********
ORDER BY domain, email ASC;

The original answer for SQL Server didn t work for me....

Here is a version for SQL Server...

select SUBSTRING(email,(CHARINDEX( @ ,email)+1),len(email)), count(*) 
from table_name 
group by SUBSTRING(email,(CHARINDEX( @ ,email)+1),len(email))
order by count(*) desc

work smarter not harder:

SELECT REVERSE(SUBSTRING_INDEX(REVERSE(SUBSTRING(emails.email, POSITION( @  IN emails.email)+1)), . ,2)) FROM emails