Or in a query :

where MyColum like @Letter + '%'

How about using the correct design and creating a third table?

Didn't mean to insult you in any way!

What did I say wrong?

Now that you're all vented away ..

Search this site for parameter sniffing and how it affects procs just like you described. Basically you...

Why not just Q.year, ...?

Can you show us a few exemples on the questionable keys in their tables?

Check the permissions of the users accessing the objects.

Number of posts. The incrememnts are very low at the beginning. (like 10, 25, 50, 75, 100...) While I don't remember them all I know it finally...

A deterministic function could be used for this. Just send the identity as the input parameter and you're golden. No impact on inserts or updates. However the...

Check the books online. You need to convert the data to the ainsi complient format (112 I think). That will make the column deterministic so you can index...

You wouldn't see any boost in performance in the computed column solution unless it was indexed as well...

You only need to use it with the order by clause. It has something to do with getting the best execution plan possible... but I can't elaborate much more...

HTH.

Can you convert the sp into a function so you can use it in a select?

It is considered a best pratice to ALWAYS specify the owner of the object (any object). This is one of the many reasons. Also I think you can...