>>Where t.EffectiveDate is null and ge.Month_of_file <= '20060901'

Why are you using less than or equal to in this part of your join ?

What are you expecting SQL to do...

What is the format ? What's between each field ? A TAB character ?

How have you determined that the location of tempdb is the issue ?

Maybe it's how you're using it versus where it's physically located ? Do you have long-running SQL that...

Something like this maybe ? Will get pretty ugly if there are more than 5 SOrder buckets.

SELECT Response_Code, Name, Count(Alert_Id) as 'Total_Alerts', 1 As SOrder

From Alert

WHERE (Create_Date Between @StartDate And @EndDate...

Can we assume it's SQL 2000 ? SQL 2005 provides common table expressions (CTE) which would be very useful for doing this without a temp table, but need to know...

You can use the OpenRowset() function to return a recordset from another server without having to setup a linked server.

See OpenRowset() topic in BOL.

>>unforunately I do not have access to any reference material

SQL Books on line (aka BOL) is freely available.

Read BOL on topics BULK INSERT, IDENTITY() function and #temp tables.

When you get into nested CASE statements in a Join, while syntacically correct, it can often become a code maintenance nightmare. Who's going to know what that logic is all...

>>i just can't figure out where it's getting the genre code from

One of your category table records has the wrong genre_code value.

A show belongs in a category.

A category belongs...

>>I have heard that there is a performance loss using EXISTS(SELECT * FROM ...) compared to EXISTS(SELECT NULL FROM ...),

That was only on versions 6.5 (or was it 7.0...

>>IN ERROR HANDLER: 'Column number out of range.'

I would guess an issue with referencing columns in a resultset by ordinal position instead of name.

>>Would happen to have any suggestions for my row_number() problem though would yoU?

You're doing an INSERT, when you should be doing an UPDATE.

UPDATE

t

SET

If you're asking purely from a performance perspective, then there should be no difference between the 2.

The reasons for avoiding Select * in this scenario (scenario= all columns required), are...

For problems like this, you typcially solve them by joining to a derived table which gives you the required record for each group:

Select t.MemberNbr, t.StartDate, t.EndDate, t.Plan

From YourTable As t

Inner...

Why is this even a trigger ? Sounds like typical source/target table synchronisation.

- Identify primary key column or columns

- Insert target where primary key exist in source but not target

-...