Jeff and Paul,

Thanks for all your help. I am going to try to implement Paul's approach.

Another peice of information that might be helpful. The reason we preassign a range of numbers is often times the company will send us a file of new employees...

Jeff,

To answer your question:

Do you mean to tell me that these alternate id's will NOT be used anywhere else in the database?

Yes they will be used elsewhere....

Paul,

That was very impressive! They have already started allocating ranges manually. Here is what has happened thus far.

CompanyA 882150000882151000

CompanyB 890100000890199999

CompanyC883550000883559999

CompanyD ...

Jeff, I am a little confused by your last two posts. The Alternate IDs start at 800000000 and go to 899999999. I don't see how you can get...

They'll get a new rangeid so if they first went in as IBM they will next go in as IBM2.

I will go with that unless I hear something else. I'll test the response time as well. Thanks.

The typo is an excellent point. My approach is to come up with a couple of options and then look at the pros and cons of each. You...

I know it is hard to believe but they are not worried about people needing a bigger range.

Prepopulating is tough because they may have some companies that need...

They get stopped right away. RangeID is the primary key, so I will first check to see if that RangeID exists, and if it does I exit the stored...

Yes those 3 records are the starting conditions. The example scenario would be a user enters a RangeID of 'D' and the number of Alternating ID's they want as...

First of all there is a mistake in my example. The data should be.

insert into RangeValues values ('A', 810000000, 810001000)

insert into RangeValues values ('B', 820000000, 820004000)

insert into RangeValues values...

Sorry about the lack of detail, I was trying to keep it simple, but I can see how it was not enough information.

I am trying to create a stored procedure...