Also Kiran, to John Mitchell's point, you ask a whole lot of questions on many forums that have simple and quick answers if you spend just a little time and effort on your part. Using the title to your post, it took only 4 minutes to find the article I provided the link to. It's not like you're a beginner at SQL... you first became a member of SSC more than 7 years ago.
This isn't meant as a slam... it's a suggestion that has helped me learn a whole lot and helps me avoid panic situations. Spend some time learning the product and how to use Google to help (but don't let it become a crutch like what you currently use forums for). When problems like this one occur, it'll take you a whole lot less time to come up with a solution and, if you study the code causing the problem (usually code with an accidental cross join in the form of a many-to-many inner join because someone doesn't know the data), you'll be able to prevent such things in the future.
is pronounced ree-bar and is a Modenism for R
First step towards the paradigm shift of writing Set Based code: Stop thinking about what you want to do to a row... think, instead, of what you want to do to a column.
If you think its expensive to hire a professional to do the job, wait until you hire an amateur. -- Red Adair
How to post code problemsHow to post performance problemsForum FAQs