It's hard to say without more information, but here's an article I found very useful when I ran into similar problems that did turn out to be an issue with...

You're seeing the length in bytes. Each NVARCHAR character takes up two bytes of storage.

LutzM,

Ah, you're so right. I see it now. My mistake.

E99999

F00001

...

FT9999

FU0001

...

FUB999

FUC001

...

FUCJ99

What would be the next value in the sequence?

Fair enough.:-P

Theo Spears (9/8/2011)...

If you don't wish to do this, there is an SSMS config file you can delete that will reset your keyboard shortcuts. I can't remember the details off...

I've got it! Exclude vowels from the sequences you generate. That way the only people you might offend are the Welsh.

Jeff Moden (9/8/2011)

---

I AM the reference! 😉 Do it your way and embarass your company and possibly get sued for offending someone's sensibilities. ...

LOL!

Jeff Moden (9/7/2011)

---

notoriousdba (9/7/2011)

---

I'd take Lowell's approach, though if the logic for converting the value in the identity column to the alpha-numeric value you want is non-trivial, you can easily...

I'd take Lowell's approach, though if the logic for converting the value in the identity column to the alpha-numeric value you want is non-trivial, you can easily abstract it to...

Piet,

Maybe you haven't been in this game long enough to know who Joe Celko is. Not for nothing, but if he talks, you should listen.

To constrain relationships the way you want, you could create an xref between relationship types and roles, defining which combinations were valid, then FK the Party Relationship table to the...

It seems to me you're only looking at data in two tables. Try this on for size:

SELECT a.JobReqID, a.JobReqCode, a.DateAdded, COUNT(DISTINCT c.CandidateID) AS SelectedCandidates

FROM RecruitmentDB.dbo.JobRequisition a

...

I second that. Also, I'd recommend adding a flag to all of your lookup tables to allow entries to be marked as obsolete.