Blog Post

T-SQL Tuesday #155 Round Up

,

It’s time to look back at the 155th blog party. I was the host this month, asking about Dynamic SQL. I got quite a few responses, which I’ve gone through and summarized below. If I’ve missed someone, please ping me.

The Round Up

There are some great posts, so if you are interested in any of these areas, click through and read the original post.

Rob Farley is first, as usual. He’s in Australia, so often he gets to publish close to the start of the day in the world. This month Rob writes about the dangers of dynamic SQL and how you can actually not take values of object names from the user. Instead, use their input to search sys.objects and get the value there.

Vitaly Bruk writes about how single use plans with EF cause issues, and how to solve them.

Richard Swinbank talks about how to use dynamic SQL to generate SQL code from metadata. Something I’ve used quite a bit in the past.

Erik Darling takes time to discuss the datatypes used with dynamic SQL and how you might deal with the requirement for NVARCHAR when building the string.

Ajay Dwivendi has a method for gathering SQL Server health metrics using dynamic SQL.

Aaron Bertrand gets a post in, despite being on vacation. He writes about ow you might use dynamic SQL to execute code across all databases.

Brent Ozar adds comments to Dynamic SQL. He suggest you should as well.

Oliver Van Steenlandt writes about a couple of cases. Managing different levels of aggregates and for building ETL scripts.

Raul Gonzalez reminds us of the security issues with dynamic SQL and SQL Injection.

Reitse Eskins has a lot of schemas and uses dynamic SQL to build GRANT scripts.

Shane O’Neill shows a few Dynamic SQL tricks to make it easier to debug.

Gerard Jaryczewski is new to the T-SQL Tuesday party, but skips in with a solution to a nightmare for a SQL developer.

Josh Smith gives us a three act play that is amusing to read.

Nigel Foulkes-Nock takes a moment to examine the foreach db procedure.

Kevin Martin writes about a search procedure you don’t have to write, because it’s generated.

Original post (opens in new tab)
View comments in original post (opens in new tab)

Rate

You rated this post out of 5. Change rating

Share

Share

Rate

You rated this post out of 5. Change rating