Have a table (SQL Server 2008) that the user wants to record a fixed 8 character string in. At first glance, a CHAR seems the obvious selection since this value (an 8 character ID, two alpha ...

The page is taking form-submitted data and saving it to a SQL Server database via stored procedure.<br><br>Just one problem - every time I execute the code, I get the following error:<br><br><br ...

The new VARCHAR data type with UTF-8 encoding should require less space, and filter and sorting operations should also run significantly faster. The API has been adapted accordingly.