You can move that select with the parameters in a function.

CREATE FUNCTION dbo.fnName (params list)

RETURNS TABLE

AS

RETURN Select statement with params

GO

The only way to track all those is to start a trace using the profiler. This will allow you to get all that information.

The downside is that this can...

So is that when you'll start pumping out 200 posts/day or that was just a big joke ?

Do you need data spanned on multiple days between a small range of hours/minutes for each day (from 2005/01/01 to 2005/01/03 AND only from 12:30 to 15:55 for each day)...

Little error in my solution... the nulls should be OUTSIDE the cast .

UNION ALL

Select cast(count(*) as SameDataType) as col1, null, null from dbo.SameQuery

Hey Steve I...

It's really rare that you can't rewrite sps like that to make a single statement.

So when are you crossing the big K?

Actually I was reffering to canada... but if you say europe too I'll believe you .

Maybe this could be considered cheating but it would work :

Select col1, col2, col3 from dbo.OracleTable

UNION ALL

Select cast(count(*), null, null as SameDataType as col1) from dbo.SameQuery

I checked your question but I don't know what the problem is... waiting for feedback from other members.

Also if you need ms access specific answer you might visit this site...

Maybe... not what I understood on the first read.

You can switch the cursor to a loop, but that's not gonna be a big improvement. How much logic is stored in those procs? Is is possible to...

All you have to do is put the time constraints in the variables.

Can you post some sample of the constraints so that I can be sure it's possible to do?

Yes... it makes sens that this value will be unknown for a part of the lifetime of the record.

Forget the function and use this where condition in the main proc :

Select col from dbo.MyTable where DateCol >= @DateStart and DateCol <[=] @dateEnd

Place an index on the data...