Without a table alteration, you could do this (using Matt's fine test setup)...

--testing setup

create table #recipe (recipeID int identity(1,1) primary key, recipename varchar(200))

create table #recipeline(reclineID int identity(1,1) primary key, recipeID...

As a bit of a side-bar, if you intend to join DateTime datatypes to this table, the preferred method of creating such a table would be...

--===== Here are the two...

This is what I mean...

(No character based date conversions) + (No concatenation) = Very high speed short code.

--===== Here are the two parameters you wanted

DECLARE @DateStart DATETIME

DECLARE @DateEnd ...

Ah, ok... it get it.

Still need to know though, what do you want for column names? I'm also pretty sure you'll need the row number... I guess I'm...

Heh... that's funny... hadn't thought of it that way, AnirBan. 😀

I actually have an article coming out in the very near future as to "how and why" Tally tables work...

Perfect. Thanks for the feedback.

Adrian... nice job!

Yes...

Lisa... Thanks for the feedback a couple of posts back. 🙂

Any bets? 😉

I think this one taught a bunch of people different things... 🙂

IT salaries are going down for some as Steve mentioned... and for the reasons he mentioned. I'd like to remind all of you managers out there, you get what...

Thanks for the feedback... like Gus said, though... leap years can wreak a bit of havoc if they're important.

hb21l6 (4/29/2008)

---

thanks for the replys guys.

this is the solution i came up with in the end, some borrorwed some new.

SELECT * tbl_locations

WHERE CompanyName = 'someCompanyName'

ORDER BY CONVERT(int, REPLACE(CONVERT(nvarchar, SUBSTRING(IP,...

Would you rather have a slightly more complicated database maintenance program or an impossible security situation? 😉

Thanks for the plug, Gus... the article may be found at the following URL...

http://www.sqlservercentral.com/articles/Advanced+Querying/61716/

... and Gus is right... it's nasty fast.