Does your query has joins accross the servers?

I am going to enjoy by reading your next set of articles on Avoiding Cursors :)..

From now on, if any body asks me on why we should not use cursors...

By looking at the exeuction plan i believe EXISTS is faster...

Its a good article, but do you have any questions??

Question:

Who is going to view this data?? and in what form? In Report or Front-end application.

Hi

You can use CUBE or ROLLUP to do the sum of all the rows.

Check out the below link

http://databases.about.com/od/sql/l/aacuberollup.htm

Steve, Yo...

Hi

As Grant Fritchey said, it is INNER join. But can you please provide the table structure..so that we can guide in right direction from Table Design prespective.

Hi Gila,

These are great articles but i am not able to add any comments 🙁

Hi Venki,

Thats a good way to eliminate the duplicates. i.e. Implementing all the necessary changes to eliminate the duplicate records on the source side.

It looks to me by reading all the different post, people are leaning towards to the JOIN..

Nawar.Tabaa (1/14/2009)

---

Actually the businees rule needs to insure that only one record for a period of time, so if there is a record for the same period it will return...

Jeff,

wow..its simply great to see the way you are thinking on the questions and answers...

Hi

You may want to check out the below link to delete the duplicate records:

http://support.microsoft.com/default.aspx/kb/139444

Hi, Yes we can create TRIM UDF, Thats what i am doing right now.

==> TRIM( ,'L') for doign Left-Trim

==> TRIM( ,'R') for doign Right-Trim

==> TRIM( ) for doign Trim