I just tried the "select top 1" vs "select count(*)" and indeed "select top 1" produced poorer stats.

if exists (select count(*) from DimCandidates )

print 'here'

SQL Server parse and...

I'm certainly not an expert in SSIS, but if you have allot of indexes on the table you might want to try disabling them.

Using stored procedures is generally better than ad-hoc SQL anyway in light of plan reusability, right?. Ad-hoc SQL can be parameterized sometimes, but not always.

Yeah, that's exactly what I tried too!

create index idx_t1 on t (groupid, datestamp desc) include (alias)

Maybe if there was some criteria that said beyond a certain time frame we wouldn't...

Great point about not seeing anything yet that won't produce a scan. I started hammering away and tried some indexes when it hit me that there isn't any filter...

If you want to see all of the columns, I think a ranking function would be better.

Something like this:

with ranked

as

(

select *, RANK () over (partition by groupid order by datestamp...

When you say that the records are not consecutive, do you mean that they are not physically in consecutive order in the table? If so, how are you ordering...

If

1 100 3/10/2010 3/31/2010

1 100 4/1/2010 4/10/2010

are merged into

1 100 3/10/2010 4/10/2010

Why aren’t

1 2 4/11/2010 5/15/2010

1 2 5/16/2010 4/4/2011

Merged into

1 2 4/11/2010 4/4/2011

Did you try running profiler to see what was taking so long?

Here is an interesting article I found that talks about performance issues related to gauges. http://sqlserverpedia.com/blog/sql-server-bloggers/what%E2%80%99s-up-with-the-slow-ssrs-r2-rendering-in-sharepoint-2010-integrated-mode/

I think what is happening is that SQL Server is taking your parameter as a string like this:

@P in ('Spring, Fall, Summer')

You should split the string into a table first...

Think I found the problem. I have guages on my report that are slowing it down. When I removed the guages the report ran fine. I'm really...

I haven't tried any format other than html.

Vishal,

Please go ahead and post your code.

I personally don't like the approach of capturing user credentials at the report level. It is better to do this from the database inside of a stored procedure so...