I totally missed that part and understand your pain.

For now, the logic indicates that the "wide" join you're using seems the best option with one slight modification. You can remove...

Can you give me an example on what you just said? Are you trying to do a ranking? Or am I misunderstanding you?

Partitioning (using windows) the results is possible, but...

The Quirky Update is easy to get, assuming that you already know the rules to follow.

Here's an example with your sample data.

DECLARE @Value float=0,

@id int

UPDATE t...

I'd use a cross tabs approach which seems more flexible, but that's up to you.

SELECT YEAR(DateFormCompleted) AS YearRecruited,

Hospital,

COUNT(CASE WHEN month(DateFormCompleted) = 1...

But in the advanced "tab" from your flat file connection manager, there's a data type and length defined. The truncation might be occurring in there.

If it's a currency exchange rate table, you'll always need the date. There's no use of a rate without the date. A non-clustered index makes no sense because the clustered...

How is the column defined on your flat file connection?

One reason can be that scalar functions work row by row while inline functions don't.

Or it could be that scalar functions prevent parallelism (because of the previous cause) and...

If you concatenate anything to NULL, it will return NULL. The same way as if you try to do an arithmetic operation with NULL.

You can validate for nulls.

select idx,

'[LevelID]=' +...

I used the MAX function because I'm not sure what kind of data you need, so it will aggregate the data to get a single result. You might need a...

Your problem is the double FULL OUTER JOIN as you can see if you use SELECT * to show all rows and columns.

Here's an alternative, but you should reevaluate the...

As Sean said, there are better ways to do it than a cursor. Here's an option using XML PATH which is explained in the following article: http://www.sqlservercentral.com/articles/comma+separated+list/71700/

To solve your problem,...

Since a previous poster said that everything was correct on XP but not on Server 2003, my guess is that you might want to check that you have the correct...

I was just going to mention that. Here's a revised version to include strings with no matches at all using OUTER APPLY.

WITH cteString ( ArtifactID, PATH )

...

I'd also remove the CASE (which doesn't seems to match the pattern search) and include it in the APPLY results.

WITH cteString ( ArtifactID, PATH )

...