Get next available number from table

I have an ID field that is actually a text field in the SQL table which contains an ID number for the records.  Some of the data looks like this:

myID
90456
TN945
AS903
TN946, etc.

I need to create a query to show the end user the next available ID number for the ID's starting in TN, for the ID starting with AS, and for the ID's that is all numbers.  When I try to do the top 1 in the query and then in my cfset statement try to add a 1 to get the next record, of course it is telling me 'The value "" cannot be converted to a number' since I am trying to add a number to a text field.  

How can I get these numbers?
<cfquery datasource="mydatasource" name="getIDs">
	SELECT top 1 myID
	FROM myTable
    WHERE (myID NOT LIKE 'TN%'
		and myID NOT LIKE 'AS%')
    order By myID desc
</cfquery>
 
<cfquery datasource="mydatasource" name="getTNIDs">
	SELECT myID
	FROM myTable
    WHERE myID LIKE 'TN%'
    order By myID desc
</cfquery>
 
<cfquery datasource="mydatasource" name="getASIDs">
	SELECT myID
	FROM myTable
    WHERE myID LIKE 'AS%'
    order By myID desc
</cfquery>
 
<cfoutput>
<cfset NextID = (#getIDs.myID# + 1)>
<cfset NextTNID = (#getTNIDs.myID# + 1)>
<cfset NextASID = (#getASIDs.myID# + 1)>
</cfoutput>

Open in new window

Lee R Liddick JrReporting AnalystAsked:
Who is Participating?
 
Aneesh RetnakaranConnect With a Mentor Database AdministratorCommented:
I didnt find any error
USE tempdb
go 
 
create table MyTable ( MyID varchar(10) )
insert into MyTable select 100
insert into MyTable select 200
insert into MyTable select 'TN1001'
insert into MyTable select 'TN1003'
insert into MyTable select 'AS1101'
insert into MyTable select 'AS1191'
 
SELECT top 1 cast(myID as int ) +1
FROM myTable
WHERE (myID NOT LIKE 'TN%'
    and myID NOT LIKE 'AS%')
order By myID desc
 
 
SELECT top 1 'TN' + cast(   CAST( replace(myID,'TN', '' ) as int ) +1   as varchar ) 
FROM myTable
WHERE myID LIKE 'TN%'
order By myID desc
 
SELECT top 1 'AS'  + CAST(  CAST( replace(myID,'AS', '' ) as int )  + 1   as varchar ) 
FROM myTable
WHERE myID LIKE 'AS%'
order By myID desc

Open in new window

0
 
Aneesh RetnakaranDatabase AdministratorCommented:

      SELECT top 1 cast(myID as int ) +1
      FROM myTable
    WHERE (myID NOT LIKE 'TN%'
            and myID NOT LIKE 'AS%')
    order By myID desc

 

      SELECT 'TN' + cast(   CAST( replace(myID,'TN', '' ) as int ) +1   as varchar )
      FROM myTable
    WHERE myID LIKE 'TN%'
    order By myID desc

 

      SELECT 'TN'  + CAST(  CAST( replace(myID,'AS', '' ) as int )  + 1   as varchar )
      FROM myTable
    WHERE myID LIKE 'AS%'
    order By myID desc

 






0
 
RiteshShahCommented:
can't you use something like

SELECT substring(myID,1,2) + cast(convert(int,substring(myID,3,len(myID)-1))+1 as varchar)
        FROM myTable
    WHERE myID LIKE 'TN%'
    order By myID desc


it will give you incremented number itself
0
Cloud Class® Course: SQL Server Core 2016

This course will introduce you to SQL Server Core 2016, as well as teach you about SSMS, data tools, installation, server configuration, using Management Studio, and writing and executing queries.

 
Lee R Liddick JrReporting AnalystAuthor Commented:
aneeshattingal...I am getting a CF error of 'incorrect syntax near the keyword 'as'.
0
 
RiteshShahCommented:
have you tried mine?
0
 
Lee R Liddick JrReporting AnalystAuthor Commented:
Ritesh...I already have established numbers in the tables, the end users want to be able to see what the next available number is.  Understanding that if two people do this at the same time, they may input the same number anyway.
0
 
Lee R Liddick JrReporting AnalystAuthor Commented:
Ritesh...not sure if it works or not.  It seems they also have a letter of 'a' or 'b' after some of the ID's that ended up to be duplicated.  So there are two like TN903a and TN903b.
0
 
8080_DiverCommented:
After your last post, I have to ask, "How do you define 'the next number'?"
For insance, if the ID is 90210, it would seem fairly obvious that "the next number" is 90211.  However, is "the next number" for "TN903a" going to be "TN904a" or "TN903b" (i.e. do you only increment the numeric or do you increment the alpha ending)?  Also, if "TN903" exists, is "the next number" supposed to be "TN903a".
What about "TN999a"?  If you increment the numeric, is "the next number" going to be "TN000a", "TN1000a", "TN000", or "TN1000"?  
In other words, what is the Business Rule definition of "the next number" such that there are "oh, yeah, didn't I mention . . . ", "most of the time but sometimes . . . ", or other exceptions?  Without that definition, you are not going to have a chance of meeting the requirement.
Wouldn't it be a better overall design to have 3 columns: IDPrefix (NULLable) for the TN, AS or whatever; ID (INT); and an IDSuffix (NULLable) for the trailing alpha character?  
0
 
Aneesh RetnakaranDatabase AdministratorCommented:
Can u try those SQL statements in SSMS, i am not good in coldfusion, in case it works, you can convert them to cf statements
0
 
Lee R Liddick JrReporting AnalystAuthor Commented:
aneesh...I did run the statements in SQL and got the same error.

8080...the ID's with the letter at the end is an anomoly and should not be in the calculation of the next available number.  In retrospect, that would be an ideal situation; however, I am dealing with an already 3 year established application that we have converted from a 'sharepoint' list application to a web based coldfusion app.  If I originally built this, I would have had a prefix and an autonumber to fill in the next so there would not be a need for any suffix.  Unfortunately, I do not have that luxury at this point and have to work with what I have.

So in answer to your question, if the last number was TN922b the next number would be TN923.
0
 
Lee R Liddick JrReporting AnalystAuthor Commented:
aneesh...I found what I did...I typo'd the cast to 'case'!
0
 
Lee R Liddick JrReporting AnalystAuthor Commented:
This code was a little different than your first post...not sure if that was my problem as well, but it's all working now.  Excellent help.  Thanks again!
0
 
8080_DiverCommented:
How about a UDF?
Call it with:

SELECT dbo.NextSeqNumber('TN100a') AS NextValue;

ALTER FUNCTION dbo.NextSeqNumber 
	(
	 @CurrentValue AS VarChar(10)
	)
RETURNS VarChar(10)
AS
BEGIN
	DECLARE	@TempInt		AS INT;
	DECLARE	@TempSeq		AS	INT;
	DECLARE	@TempValue	AS	VARCHAR(10);
	DECLARE	@TempPrefix	AS	VarChar(03);
	DECLARE	@TempSuffix	AS	VarChar(01);
	DECLARE	@HasSuffix	AS Char(01);
	DECLARE	@HasPrefix	AS	Char(01);
	
	SET	@TempSuffix	=	RIGHT(@CurrentValue, 1);
	SET	@TempInt	=	ISNUMERIC(@TempSuffix);
 
	IF	(@TempInt = 1)
	BEGIN
		SET	@HasSuffix	=	'N';
		SET	@TempValue	=	@CurrentValue;
		SET	@TempSuffix	=	'';
	END
	ELSE
	BEGIN
		SET	@HasSuffix	=	'Y';
		SET	@TempValue	=	LEFT(@CurrentValue, LEN(@CurrentValue) - 1);
	END
	
	SET	@TempPrefix	=	'';
	SET	@TempInt	=	ISNUMERIC(@TempValue);
	
	WHILE	(@TempInt = 0)
	BEGIN
		SET	@TempPrefix	=	@TempPrefix + LEFT(@TempValue, 1);
		SET	@TempValue	=	RIGHT(@TempValue, LEN(@TempValue) - 1);
		SET	@TempInt	=	ISNUMERIC(@TempValue);
	END
	
	SET	@TempSeq	=	CAST(@TempValue	As	INT) + 1;
	SET	@TempValue	=	@TempPrefix	+	CAST(@TempSeq	AS	VarChar(07))	+	@TempSuffix;
	
	
	RETURN @TempValue
END

Open in new window

0
 
8080_DiverCommented:
Just a passing curiosity but, you do realize that the selected solution is going to fail whenever it encounters a trailing aplha character, don't you? ;-)
0
Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.

All Courses

From novice to tech pro — start learning today.