I was wondering.  How would you take a solution similar to yours but make the column headers equal the value of a column of record.  For example:

declare @t...

how would you make this extensible?  How would you design this to allow for the addition of new Criteria (wff.Gender etc...)?

Thanks Noeld.  My original system design was to encapsulate this in a process and archive the results.  Unfortunately, the project requestor wants to be able to run this for any...

I appreciate the response, but i think your solution wont work for us because you are grouping by month.  I need to group the results by groups of customers within...

thanks for the suggestions.

Well, it looks like it was an index issue.  I ran the query statement through the tuning wizard and found that i did not have an index on the columns. ...

That's what i was thinking.  The only difference i could see in the execution plans is that the use of the additional where criteria eliminated the a HASH Match/Join step.  I guess...

Here's a mock up of the tables.  Keep in mind the ContractTable will have approximately 1200 records and the transactiontable will have over a million records.

-- drop table #contracttable

-- drop...

Currently, we have only 2 contractid's.  The contractid determines which account we use to sum transactions on.  The contractid exist in only 1 table.  it's used to categorized the records...

I understand what you're saying.  What i dont get is the "Case When ContractID = 2" acts the same as

Case when Contractid = 2

I appreciate the feedback.  It wasnt until I gave it some more thought that i realized the Master Database contains the db replicated flag.  Thanks again.

Im not sure how a trigger would solve this problem.  I either want to run a stored procedure to create the views dynamically based on a schedule or allow a...

I agree that a standard spreadsheet format would be best.  Unfortunately the spreadsheet im dealing with is an ever evolving one.  Basically, the columns represent new attributes for a product. ...

You're correct.  The id value in my table should be ID 1 for each matching column and value.  I apologize for the confusion.

Ah the wonders of Set Base solutions...  Yes the left join worked wonders.  I used case to designate the different pay amounts.  So far everything works great.  Thanks for all...