Reviewing The New DACPAC Code Analysis Rules For T-SQL

Reviewing The New DACPAC Code Analysis Rules For T-SQL

You can read the announcement post here.

Going Further

If this is the kind of SQL Server stuff you love learning about, you’ll love my training. I’m offering a 75% discount to my blog readers if you click from here. I’m also available for consulting if you just don’t have time for that, and need to solve database performance problems quickly. You can also get a quick, low cost health check with no phone time required.

5 thoughts on “Reviewing The New DACPAC Code Analysis Rules For T-SQL

  1. I appreciate the round-up of these. I had seen the plug-in before but I don’t think the “SQL Smells” were part of the checks before. I also appreciate that some can be ignored if needed when you’ve chosen an option that works well for your codebase but isn’t a best practice. (like using a cursor for that one task that just … needs a cursor to work well)

    I’ve got to do some playing with this now to see how it plays out with one of the code bases I support. I think the code analysis might cry a little, though. 🙂

    1. Yeah, I get it, but like… it’s really easy to hit the integer max these days. The pain of converting to big ints is significant. All the posts that tell you about doing it with page compression don’t go into the many caveats.

Comments are closed.