We shouldn't accept that... the more info we get the better, and the more often we'll get it.

You're using sql server and he doesn't want you to use stored procs????

Is there a real reason behind is madness?

Dropped it after the insert or after the select??

ALTER TABLE dbo.TableName

ADD ColName datetime not null default (GetDate())

Well the first answer is do it client side. But we always follow with this :

IF Object_id('ListTableColumns') > 0

DROP FUNCTION ListTableColumns

GO

CREATE FUNCTION dbo.ListTableColumns (@TableID as int)

RETURNS varchar(8000)

AS

BEGIN

Declare @Items...

One other thing that can screw this up :

2+ cpus (multiple threads reading)

or

another process already reading the same data >> the 2nd query joins the fetching of the first...

This is assuming that the reporting will only ever be monthly and that would be a huge design flaw if you want my opinion.

I like that if Chris .

We'll see...

Make sure you don't use a function on a column (bad for performance).

Also please not that 90 days and 3 months are not the same thing

Still waiting to test my theory .

Can you post the final code so that it may help somebody else?

SOL?

That one's gonna be hard to beat .

Can we see the final code??