Comments on: SQL SERVER – 2008 – Enhenced TRIM() Function – Remove Trailing Spaces, Leading Spaces, White Space, Tabs, Carriage Returns, Line Feeds

By: madhivanan

madhivanan — Mon, 24 Oct 2011 15:58:26 +0000

This will give you what you want

select right(col,3) from table

By: ernie

ernie — Fri, 21 Oct 2011 07:19:23 +0000

is it possible to trim data based on the number of characters and not just the spaces in an sql query. example: i just wanna get the last 3 digits of an int column which already has 50000 rows.

By: Madhivanan

Madhivanan — Mon, 08 Mar 2010 09:55:11 +0000

There is no built-in function in SQL Server 2008 for trim
If you get input values from front end application, remove the spaces there

By: Padma

Padma — Thu, 13 Aug 2009 22:25:29 +0000

Pinal,

In my working environment we are accepting multiple inputs (parameters) and we have to trim the white spaces before and after the input value.

I have the function which performs very badly, takes lots of time. Now we are in plan of moving to SQL server 2008. I have heard that there is a function trim() available in SQL 2008. Can you please help me with the code which trims spaces for multiple comma separated input values.

By: SQL SERVER – Connect Item – Vote for Feature Request Function TRIM Journey to SQL Authority with Pinal Dave

Wed, 03 Jun 2009 01:31:57 +0000

[...] SQL SERVER – 2008 – Enhenced TRIM() Function – Remove Trailing Spaces, Leading Spaces, White S… [...]

By: LOL@Enhenced

LOL@Enhenced — Mon, 22 Dec 2008 22:36:13 +0000

I’m going with phil’s function. It doesn’t do any more or less than what I want.

By: Speednet

Speednet — Sat, 18 Oct 2008 15:09:05 +0000

@phil Factor: If you try my version of SuperTrim, you will see that it does NOT trim to 8000 characters.

By: Nathan

Nathan — Fri, 17 Oct 2008 16:19:59 +0000

Pinal, thanks for all your posts. May I suggest using the spelling “Enhanced” instead of “Enhenced” in your post?

Thanks again!

By: phil Factor

phil Factor — Sun, 12 Oct 2008 10:41:41 +0000

The function definitely just returns the first 8000 characters. This version definitely works a lot better

alter FUNCTION dbo.LTrimX(@str VARCHAR(MAX)) RETURNS VARCHAR(MAX)
AS
BEGIN
DECLARE @trimchars VARCHAR(10)
SET @trimchars = CHAR(9)+CHAR(10)+CHAR(13)+CHAR(32)
IF @str LIKE ‘[' + @trimchars + ']%’
SET @str =STUFF ( @str , 1 , PATINDEX(‘%[^' + @trimchars + ']%’, @str)-1 ,” )
RETURN @str
END
GO

By: Phil Factor

Phil Factor — Sun, 12 Oct 2008 10:14:04 +0000

Oh dear, surely, unless I’m missing something these functions will just return the first 8000 characters if they do a Trim, and so could cause havoc if someone uses it in SQL Server 2005/8 without realising its limitations, or you have it in place in a production system and the data changes. You’d do better if it took and returned Varchar(8000). Then it might flag up the weakness in the algorithm.

By: Speednet

Speednet — Sat, 11 Oct 2008 04:43:24 +0000

Hi Pinal,

May I suggest some improvements?

I tend to call my whitespace trimmers “SuperTrim” functions, so please excuse the difference in naming.

(This will probably lose its indenting when I paste it.)

———
CREATE FUNCTION dbo.SuperTrimLeft(@str varchar(MAX)) RETURNS varchar(MAX)
AS
BEGIN
IF (ASCII(LEFT(@str, 1)) < 33) BEGIN
SET @str = STUFF(@str, 1, PATINDEX(‘%[^'+CHAR(0)+'-'+CHAR(32)+']%’, @str) – 1, ”);
END;

RETURN @str;
END;
———

I think it’s a big performance increase, because it does a numeric test of the first character, rather than a relatively expensive pattern test. If the first character is not a space or some other control character, no pattern is tested at all.

Then, instead of testing for specific control characters, why not test for the whole range of zero (0) through 32 (space)?

The function above does the test for first non-whitespace char and the trimming all in one statement.

I couldn’t think of a faster or more efficient way to do it. I did some testing, and it seemed to work well.

I haven’t looked at different ways to do SuperTrimRight yet, but the ways you outlined should work with this function OK.

Thanks for the great SQL blog!

-Todd (“Speednet”)