Sql-server – Remove last character in selected column

sql serversql-server-2008-r2

Query:

select * from aa;

Output:

ID  FirstName   LastName    City
-----------------------------------
29  Abcrdrr     hai         chennai
67  adf         adsd        adsf
1   John        vinoth      CITY

I want to display the lastname column without last character. I am using following queries:

Declare @name as varchar(100);

select @name = city from aa
Select @name, left(@name, len(@name)-1) as AfterRemoveLastCharacter

But output will come first row only

Best Answer

"The first shall be last, and the last shall be first"

REVERSE(STUFF ( REVERSE(lastname), 1, 1, ''))

Related Solutions

Sql-server – Table structure for many custom profiles

It always pains me to suggest it but theres a reasonable case for making use of an XML column here.

Create appropriate tables to handle commonly used fields i.e. name, address, email, age, gender etc. I'd be tempted to store the custom fieldsets as an XML column. Once the number of subscribers they are emailing reaches a level where performance may become a problem, trigger a notification to the DBA so they can review the custom fieldsets created by your users and see if there is justification for moving them out of XML columns to defined sub-type tables.

Obviously you end up with two code paths for handling XML and sub-type definitions but you retain flexibility while having a process for dealing with the potential performance implications.

If SQL2008 was an option, I'd consider making use of sparse columns for the custom fields (generic definitions, along the lines you mentioned) and combine with filtered indexes for the larger customers.

SQL Server to MySQL Migration – Remove UCS-2 Surrogate Pairs

You need to take the data from UTF-8 and convert it into UCS-2LE using something like iconv. For example, using the character in your example:

echo "010000: dcb3" | xxd -r -s -0x10000 | iconv -f "UTF-8" -t "UCS-2LE" | xxd
0000000: 3307

Now I'm not sure what character UTF-8 \xdcb3 is, but apparently it's correct translation to UCS-2LE is \U0733. If you have \0xDCB3 in the SQL Server it means it was not translated into UCS-2LE before import. You should not have surrogates in the NVARCHAR fields, UCS-2 is "surrogate agnostic". See UCS-2 vs. UTF-16 (not quite Kramer vs. Kramer).

I'm not an expert in the MySQL tool set so I can't say what step is missing that was supposed to do the iconv.

Update

to locate the records with surrogates you must turn to the binary representation, since any character function will threat the surrogates as 'special':. Luckily the string manipulation functions work on binary too with the expected semantics. Eg. CHARINDEX:

insert into test(a) values  (N'a');
insert into test(a) values  (NCHAR(0xdc83));
insert into test(a) values  (N'b');
go

select * from test where charindex(0x83dc, cast(a as varbinary(8000))) > 0;

Best Answer

Related Solutions

Sql-server – Table structure for many custom profiles

SQL Server to MySQL Migration – Remove UCS-2 Surrogate Pairs

Related Question