30000 records will not affect the performance by removing the column. It may affect your performance if you have clustered index on it.

Nice article..

Thanks gail...

I have defined @split_string, SplitString (column) as varchar(8000). For 2005 or later users it can be varchar(max) (for too large string process)which will not affect the performance..

Hi ezhil,

please check this article ..

This article has two types of split.

1. XML split

2. SQL Function (Basic SQL string split for SQL 2000 or later)

http://www.sqlservercentral.com/articles/XML/66932/

With regards,

Rafidheen.M

Hi all,

sorry for the late reply...

I agreed with performance issue of SQL function incase of too large string needs to be split.

hence, i have slightly modified the SQL function which...

Hi all,

Its a new way to split the string using XML. I have written a SQL function to split the string without using XML. Please refer the below code...

CREATE function...

This can be write like this and avoid CASE statements from WHERE clause..

CREATE PROC test

@Stamp datetime,

@FirstName varchar(25) = NULL,

@Surname varchar(25) = NULL,

@Age int = NULL,

@Address1 varchar(40) = NULL

AS

BEGIN

DECLARE @Today BIT

SELECT...