SQL SERVER – Connect Item – Vote for Feature Request Function TRIM

Till date, I have met the SQL Server Product Team twice: first time at SQL Server MVP Meet, Seattle, and second time at TechEd India 2009, Hyderabad. At both the times, I have put forth one request to the product team regarding implementing of function Trim(). As per my opinion, this is the most demanded feature of SQL Server. Almost all the programming languages have function TRIM() which removes space leading and any word that follows. However, SQL Server does not have TRIM() function. It has LTRIM() and RTRIM() functions, which when combined together LTRIM(RTRIM()) works like the expected TRIM() function – which I am proposing.

I have submitted the connect item for requesting TRIM() function. I am requesting all the users to vote for connect item and bring it up to the notice of SQL Server Product Group.

Microsoft Connect SQL Server – Feature Request TRIM()

If you are a SQL Server DBA you can think of the benefits you will gain after this function is implemented; you will save time and energy and there will be no more frustration! It is our moral duty to spread the word for this item and vote for implementation of this feature.

I had previously written the following three articles, which covers workaround, tricks and enhanced functions related to TRIM().

SQL SERVER – TRIM() Function – UDF TRIM()

SQL SERVER – 2008 – TRIM() Function – User Defined Function

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

Reference : Pinal Dave (https://blog.sqlauthority.com)

SQL Function
Previous Post
SQLAuthority News – Summary of TechEd India 2009 – A Grand Event
Next Post
SQL SERVER – What is Interim Table – Simple Definition of Interim Table

Related Posts

3 Comments. Leave new

  • Brian Tkatch
    June 3, 2009 5:59 pm

    @Pinal

    Typo in the article. “Freature” has an extra “r”.

    Also, just added my vote. Thanx for bringing it up.

    Reply
  • It looks like the feature request got created on the onecare connect and not the SQL Server connect.

    Reply

Leave a Reply