Hi,

I am running that on SQL server 2005 SP2. Actually it seems to be due to Parallelism, the sql engine shares the work load on the for processors which in...

Actually my question was: Is it possible to create a function and stored procedure with a date variable and then, instead of the sql engine directly creating the execute plan...

Already tried the covering index, this had no impact on the performance.

Is there a way to tell the sql engine to skip execution plan?

A very strange one: if I limit my query to a specific Account my partitioned view is used correctly (access only one table):

DECLARE @COBDate SMALLDATETIME

SELECT @COBDate = '20080305';

SELECT Account,SUM(Amount) FROM...

Hi,

I have tried many ways to fix that but couldn't find a solution yet (I am not very keen in using dynamic SQL).

Basically when I run the following query:

SELECT COBDate,Account,SUM(Amount)...

No index on COBDate, find below the generic schema of one ut_rules_yyyy_mm_dd table:

CREATE TABLE [dbo].[ut_rules_2008_02_28](

[COBDate] [smalldatetime] NOT NULL,

[RuleID] [int] NOT NULL,

[IrecID] [int] NOT NULL,

[NB] [bigint] NULL,

[Account] [varchar](255) COLLATE Latin1_General_CI_AS NULL,

[Portfolio]...

Phillip, what you proposed above works exactly the same way as my previous function, the performance is very poor. But if I hardcode the date into the SQL statement the...

There is really no way to create user defined function to access one table at time as below? Maybe I need to add something to the WHERE clause to help...

Thanks Phillip,

I understand, but one of the advantage of the partitioned view is to access dynamically one table at a time. So in my case I want to create a...

The steps you mentioned in your previous post is exactly what I am doing on a daily basis.

I really don't see the advantage of partitioned view as I thought their...