Also, as far as the query differences.

Sql 2000 optimizer is very different than SQL 2005.

SQL 2005 usually picks a better execution plan.

However, SQL 2000 processed table variables much faster...

The tool makes recommendation absent other activities. It only tells you things it would use if they existed for the particular statement(s) you selected.

I usually review the reccomendations each individually...

I do not think you can accomplish what you need using the WITH command, since you have multiple detail level lines using both element and attribute centric values.

I played with...

Look at this

http://forums.microsoft.com/MSDN/ShowPost.aspx?PostID=2012999&SiteID=1

oj suggested using an update on an openquery()

if you put an identity column or primary key on your search table.

you could create another table that you write the primary key / identity to when they get...

if f2 is named ell then you can also search sysobjects for distinct names (places) referencing it.

In case some other areas that are not actively being used (which profiler will...

did the statement you were trying to tune have a temp (#) table in it?

I have seen the advisor error when trying to tune a procedure using one.

the compiler is probably picking a different execution plan than it was previously.

I would start there.

try something like....

Dim crptApp As CRAXDRT.Application

Dim crptParmDefs As CRAXDRT.ParameterFieldDefinitions

Dim crptParmDef As CRAXDRT.ParameterFieldDefinition

...

I would think you would only come across data such as

Old Note

__________________

blah blah blah.... COR

PORATE blah blah

when they reached the end of the first line.

so you might check against...

try this

SELECT @cmd = 'DECLARE @Sum int; SELECT @SUM = SUM(used) FROM ' + @dbname +

'..sysindexes WHERE indid in (0, 1, 255));

UPDATE #sptspace SET unused = reserved - @Sum FROM...

select left(col1, 10) as col1,

left(col2, 10) as col2,

left(col3, 10) as col3

try the sysfiles table for the database you are concerned with.

you do not actually need the derived table logic.

you could do the math as part of the aggregated select if you wanted as well.

I was hoping the derived table just...

you should just hav to move your left join outside the derived table (V) as such

SELECT

pr2.presenterName,

V.PresenterID,

V.VoteFor,

CAST(V.VoteFor * 1.00 / @TotalVotes as Decimal(3,2)) as VotePercentage

FROM (--get votes for presenter

SELECT

pr2.PresenterID,

SUM( CASE WHEN...