See, if this helps:

http://www.microsoft.com/technet/prodtechnol/sql/2000/maintain/ss2kidbp.mspx

While a number might not be helpful in your case, have you considered creating a permanent date table?

Btw, let me say, I work as an asset manager, and SQL Server isn't...

See, if this helps:

http://www.microsoft.com/resources/documentation/sql/2000/all/reskit/en-us/part3/c1161.mspx

Do a forum search here. This topic has been discussed here many times recently.

The position of a column in a table is completely irrelevant for the relational engine. Just a matter of "good looking". There are also very few implications on the storage...

You can read about it in BOL under "data type precedences".

Explicitely convert this value to varchar should do the trick.

And let me add, that it is a ggod idea NOT...

Well, since both methods can't use an index anyway, don't expect good performance on larger tables. I'm not that much into Full-Text Searching, however it might be an idea to...

Somehow I miss the only "correct" answer to this question:

Do this at the presentational layer of your app! That's not really a job for the server. But (un)fortunately MS thinks...

I bet you'll already find something like this here in the script section.

Glad to hear that

You're welcome!

Well, sometimes it is useful to read the thread before posting

See the two postings before yours.

Without knowing your table structure and the statement you use, this is probably not much than guessing, but I assume you have no column or combination of column to uniquely...

Yes, either you have Enterprise Edition or Personal Edition.

Anyway, a quick overview on the differences between each edition you can find in BOL when you look at "Maximum Capacity Specifications".