New answers tagged collation
0
A further aside that is relevant to your situation: I would recommend passing dates into SQL Server in ISO 8601 format (or a close approximation to it), as that's the least likely to be misinterpreted. SQL Server 2000 seems happy with accepting dates in yyyy-mm-dd hh:mm:ss format.
1
As stated by other posters, datetime values are stored as datetime values, not as strings. If you want to get technical, they are stored as two integers - one representing days and the other representing clock ticks (3.33ms for the datetime datatype).
I agree with you in not wanting to use CONVERT() on every field. I feel that the correct place for ...
5
As stated in the comments, dates are not stored as "dates". They are actually stored as numbers. So there is no need to worry about that side of things. You can change the default output though by changing your language setting.
EXEC sp_configure 'default language', '23';
GO
RECONFIGURE
GO
This is the setting for British English. You can see all of ...
4
SQL server must version the collations. Since collations determine sort order of data persisted in the database the collation must be guaranteed to remain stable between the releases. Otherwise a collation change (eg. fixing a bug in a collation) with a new release of Windows it would result in two rows int he database to sort differently before and after ...
6
The one without the code is a version 90 (SQL Server 2005) collation, used by previous version of Windows / SQL Server. 100 (SQL Server 2008) is newer, and 110 (SQL Server 2012) is newer still.
There's a bit of an overview of the differences in the SQL Server 2008 documentation, here, however it doesn't go into great detail.
If you're developing a new ...
Top 50 recent answers are included
