<p>With the age of text messages and things like that, what's a good way to store phone numbers in a database?</p>

<p>In the USA, text messages are handled by phone numbers but in other countries I hear they use email addresses so I guess there needs to be a way to differentiate between countries that use cell phone numbers as their address.  </p>

<p>Addition:
For example, people in the USA might use 432-342-3333 or 1-432-342-3333 while in the UK they might use +44 800 400000 or they might even leave out the 44.  The 44 and the 1 makes a difference when automatically sending out SMS.  However, checking the phone number for each country can get tedious.  In this case, would you split the country code or would you merge it into a single column and deal it with it there?  </p>

I don't know if you have read these two questions, but they might help you a little.
Phone Number Columns in a Database
Is there a standard for storing normalized phone numbers in a database?
Perhaps it would be wise to store the type of number (landline, cell, fax) and/or the messages that can be received on it (voice, text, email). Note that in the US, it is also possible to send text messages to a phone via email, but I believe that is dependent on the carrier.