<?xml version="1.0" encoding="utf-8" standalone="yes"?><rss version="2.0" xmlns:atom="http://www.w3.org/2005/Atom"><channel><title>SQL Server on Ben Rodríguez</title><link>https://brodriguezv.com/categories/sql-server/</link><description>Recent content in SQL Server on Ben Rodríguez</description><generator>Hugo -- gohugo.io</generator><language>en</language><lastBuildDate>Wed, 04 Sep 2019 00:00:00 +0000</lastBuildDate><atom:link href="https://brodriguezv.com/categories/sql-server/index.xml" rel="self" type="application/rss+xml"/><item><title>Using STRING_SPLIT in SQL Server for Stored Procedures and Reporting</title><link>https://brodriguezv.com/posts/sql-server-string-split-examples/</link><pubDate>Wed, 04 Sep 2019 00:00:00 +0000</pubDate><guid>https://brodriguezv.com/posts/sql-server-string-split-examples/</guid><description>&lt;p>Hello and welcome back to another post!&lt;/p>
&lt;p>Recently, I was reviewing some stored procedures used to generate reports. These procedures accepted several parameters — some nullable, others allowing multiple values.&lt;/p></description></item><item><title>STRING_AGG in SQL Server: A Better Alternative to FOR XML PATH</title><link>https://brodriguezv.com/posts/string-agg-vs-for-xml-path-sql-server/</link><pubDate>Thu, 30 May 2019 00:00:00 +0000</pubDate><guid>https://brodriguezv.com/posts/string-agg-vs-for-xml-path-sql-server/</guid><description>&lt;p>Hello again!&lt;/p>
&lt;p>How many times have you needed to create a list of values separated by commas? I&amp;rsquo;ve been in that situation many times, and I&amp;rsquo;m sure you have too.&lt;/p>
&lt;p>Before SQL Server 2017, doing this usually meant ugly XML tricks like &lt;code>STUFF&lt;/code> and &lt;code>FOR XML PATH&lt;/code>.&lt;/p></description></item></channel></rss>