LOL, it sure is.

LOL, I know, I am guessing it's a FUNCTION!!!

YES!!!, thank you very much!!!

Nope, this proc was undocumented until the last release of books online.

When the optimizer runs the query, it will first look at the constraints and should rule out using the tables that do not fulfill the contraint.  From that it will use...

Then I would use govinn's solution.  I believe you would have to apply a clustered index to the fax number to order the data the way you need it when...

You sure will receive that error if you transaction fills up.  That is why you try to find the max size of your transaction log and set an alert to...

Wouldn't it be a problem using those sequence numbers if output was in fax number order?  What happens when new fax number is added?

Adding another sequenced number would probably make things more complex.

Given the information I have, I would think you would have to count these records as you go through the resultset...

First thing is that you want to avoid using auto grow on your transaction logs.  Set a hard limit and have SQL report when it is within 10-15% hitting that...

I am not sure the fax number will help you, but what kind of unique reference are you using?

I don't think anything is documented.  We are implementing SOX too and I am guessing most of these "rules" are coming from someone's hiney.  It's all subjective at this point. ...

If you place constraints on each of your partitioned tables, only the table that matches the constraint will be queried.  This is from what I remember from a Seminar at...

You could try backing up the database and restoring it on your system.

I agree with Jo, upgrade memory.  But you also want to research the offending query. 

Questions

What is the level of the locks?

What kind of locks are you experiencing?