This is where normalization would be your friend, but I guess that this is out of the question. I'm afraid I can't help you much with this.

Your timing couldn't be much better :

OCR

This is not a final answer but you'll know what you're looking for at least.

HTH. Make sure you don't forget the tip about between... might save you a lot of troubles.

Books online > Convert, there's a huge section about the datetime in there. You need to learn to find this stuff on your own. We can't show you...

I'm showing you the syntax, you have to understand it and then use it for your original query.

I'm not trying to insult you in any, but if you tell me you have 0 experience, you need to buy a course or follow a course... this site is...

Follow this.. can't help you without ALL that info :

Help us help you

HTH. BTW, 3 to 13 is not 10 rows, it's 11, but I guess you figured it out from the code sample .

If you don't change to varchar, you keep the presentation format of the datetime.

Stupid question here... what programming/database design formation do you have?

Here's a simple. highlight your tables in EM, hit copy, then paste here.

little conversion info :

0x08 = 8

0x10 = 10

0x40 = 64

0x80 = 128

err, wrong answer.

I don't think there is... but I haven't searched that info long.

9 = 8 + 1

56 = 32 + 16 + 8

Check out all those attributes, those are cumulative for a single column.

Sushila came up with it as a joke, but now I'm keeping it. So the joke's on her .

Check this out : Select RIGHT('0' + CAST(DatePart(MM, GetDate()) AS Varchar(2)), 2)