Skip to main content

New Functions in SQL Server 2017.


1. TRANSLATE: It basically takes a string as input and then translates the characters with some new characters, see below 

Syntax:  TRANSLATE ( inputString, characters, translations)

For Example : 

SELECT TRANSLATE ('4*{13+13}/[8-4]','[]{}','()()')

Output : 4*(13+13)/(8-4)

This function is work as REPLACE function. but TRANSLATE function is easier to use and also useful when we have to replace more than one value in the string.


2. CONCATE_WS:  It simply concats all input arguments with the specified input delimiter.

Syntax : CONCAT_WS ( separator, argument1, argument1, [argumentN]… )

For Example :

SELECT CONCAT_WS(',','Count', 'nikhil', 'hardik', 'nilesh', 'sandip' ) AS counter;

Output : nikhil, hardik, nilesh, sandip


3. TRIM:  It simply works as the C# trim function, removes all spaces from start and end of the string.

Syntax: TRIM(inputString)

For Example :

SELECT TRIM('     Nikhil Sangani    ') AS result;

Output : Nikhil Sangani

It removes only space from start and ends, not between the word and string.



4. String_AGG:  It will used to create single comma-separated string.

Syntax: String_AGG(column name,',')

For Example :
create table names ( [name] varchar(50) )go 

insert into names values ('nikhil'),('mikin'),('nikunj'),('dharmesh')

Here I have used stuff


select stuff((select ',' + [name] as [text()] 
from names for xml path('')),1,1,'')

Here I have used string_agg


select string_agg([name],',') from names

Output : nikhil,mikin,nikunj,dharmesh

Comments

Popular posts from this blog

How to write Unit Tests in .net

Unit tests are automated tests that verify the behavior code like methods and functions. Writing unit tests is crucial to clean coding, as they help ensure your code works as intended and catches bugs early in the development process. I can share some tips for writing effective unit tests: Write tests for all public methods Every public method in your code should have a corresponding unit test. This helps ensure that your code behaves correctly and catches any unexpected behavior early. public class Calculator { public int Add(int a, int b) { return a + b; } } [TestClass] public class CalculatorTests { [TestMethod] public void Add_ShouldReturnCorrectSum() { // Arrange Calculator calculator = new Calculator(); int a = 1; int b = 2; // Act int result = calculator.Add(a, b); // Assert Assert.AreEqual(3, result); } } Test boundary conditions  Make sure to test boundary conditions, such a...

What to choose between .NET Core and .NET?

 .NET Framework is a better choice if you: you don't have enough time time to learn new technology. Need a stable environment to work in. Have nearer release schedules. you are already working on an existing app and extending its functionality. If already have an existing team with .NET expertise and building production-ready software. Do not want to deal with continuous upgrades and changes. Building Windows client applications using Windows Forms or WPF .NET Core is a better choice if you: IF you wanted to deploy your app on Windows, Linux, and Mac operating systems. Are not afraid of learning new things. Are not afraid of breaking and fixing things since .NET Core is not fully matured yet. When you are learning .NET. work on open source.