Well if you are not going to post the information requested then you are on your own to try and fix the problem.  No one here will be able to...

John.

Could you post your actual query? Maybe something else is wrong that can be fixed to return your performance.

I do on a server with a case sensitive collation setting. 

My point was that no matter what collation is selected, the query will result in a match when using UPPER()...

Sure.  Something like this will return 2 result sets

create procedure test

as

set nocount on

select * from master..sysobjects

select * from master..syscolumns

go

I believe that you don't need the subselects.  Table functions can be used just like any other table so the following syntax will also work:

FROM dbo.fnWTRCenPrtDivData(@chr_div, @vch_portfolio_no ) AS  fnWTRCenPrtDivData...

Riyaz,

By doing what you've described, a case INSENSITVE search will result.  The following results in a match even though they are different cases.

declare @fac varchar(20)

        ,@fac2 varchar(20)

select...

The maximum size for a VARCHAR field is 8000 characters.  The maximum number of bytes per row is 8060 in SQL 2000.  This allowed for upto 60 bytes of other...

It is not strange if you know the order in which the various parts of a SQL query are processed and become available to later parts.  Here is a link...

You cannot use aliased columns defined in a select later on in the same select statement

This fails:  select name, m1prod as cumsum1, cumsum1 + m2prod as cumsum2 from test

You may...

You could try something like this to avoid looping:

--Build a table of numbers, you may want to make it a real table because it is a good tool to...

Why are you focusing on an example that may have been poorly constucted for an truely international system.  However, there are system in place that only deal with with people...

Mark,

I was just making a point about storing attributes with the entity.  I believe you agree that the 3 table solution is way overnormalized

I would probably declare person record as:

create...

Maybe my system is modeled so that the only people in the database will be ones born in the US, say a database of all births for a hospital corporation operating...

I agree that you rarely need more than 10 columns to identify an instance of an entity but what about attributes of that entity?

Would you propose something like this to...

Try this:

select COALESCE(cnts.cnt, 0) 'Received Applicants', jp.JobPosting_ID,  jp.Job_Title, jp.Job_Location, jp.Job_ZipCode

from Job_Posting_Table jp

left outer join (select count(*) cnt, jp.JobPosting_ID

                 from Job_Posting_Table jp

                 cross join Applicant_Table a

                 inner join Zip z1

                 on...