Got a question a while ago how to solve a problem that involved a SQL stored procedure containing the use of \u2018IN\u2019 whose data you submitted to the procedure. This was solved as many solve it, with dynamic SQL. This can be likened to building your SQL query from strings in your SP and then executing the query. For example<\/p>\n\n\n\n
CREATE PROC foobar @ids as nvarchar(500) as\nbegin\n declare @sql as varchar(500)\n SET @sql='select foo from bar where foo_id in ('+@ids+')'\n \n ...\n<\/pre>\n\n\n\n\u2018ids\u2019 here is a comma-separated list of the id’s that we want to do our look up against. The dynamic SQL query is not part of our SP but runs in its own scope. The disadvantage of this approach, however, is that it is not so easy for the query optimizer to be able to figure out how to best run your query. In addition to this, users of our SP must now also have SELECT rights on all tables from which we in our dynamic query retrieve data. You do not need this for an SP as the rights are set to the SP and it then does not matter which tables our SP retrieves data from. Dynamically generating your query can also leave the door open for SQL injections. If you find yourself in a situation where you need to use dynamic SQL, try always executing them with \u2018sp_executesql\u2019.<\/p>\n\n\n\n
One way to keep the ability to dynamically send data to \u2018IN\u2019 but avoid dynamic SQL is to create a function that splits your comma separated list and saves the values \u200b\u200bin a temporary table which you then use for your look up.<\/p>\n\n\n\n
A function for splitting a string can be done in many ways. Below is a variant that makes it possible to choose which character you want to split.<\/p>\n\n\n\n
CREATE FUNCTION dbo.Split(@String varchar(8000),\n @Delimiter char(1))\nreturns @temptable TABLE (items varchar(8000))\nas\nbegin\ndeclare @idx int\ndeclare @slice varchar(8000)\n \n select @idx = 1\n if len(@String)<1 or @String is null return\n \n while @idx!= 0\n begin 14 set @idx = charindex(@Delimiter,@String)\n \n if @idx!=0 16 set @slice = left(@String,@idx - 1)\n else 18 set @slice = @String 19 20 if(len(@slice)>0)\n \n insert into @temptable(Items) values(@slice)\n \n set @String = right(@String,len(@String) - @idx)\n \n if len(@String) = 0 break\n \n end\n return\nend<\/pre>\n\n\n\nNow you can use this feature and split your string containing your id’s.<\/p>\n\n\n\n
CREATE PROC foobar @ids as nvarchar(500) as\nbegin\n declare @sql as varchar(500)\n \n SELECT foo FROM bar WHERE foo_id IN(SELECT CONVERT(int, items) FROM dbo.Split(@ids, ','))\n \n...\n<\/pre>\n\n\n\nHowever, dynamic SQL is not always bad and can sometimes be just the way to go. So test both solutions and see what works best for your particular purpose. But keep an eye on the security details.<\/p>","protected":false},"excerpt":{"rendered":"