Code Analysis

External Article

Database Code Analysis

  • Article

Database code analysis will reduce the number of 'code smells' that creep into your database builds. It will alert the team to mistakes or omissions, such as missing indexes, that are likely to cause performance problems in production. It will allow the Governance and Operations team visibility into production readiness of the code, warning them of security loopholes and vulnerabilities. William Brewer describes the two technical approaches to database code analysis, static and dynamic, and suggests some tools that can help you get started.

2017-08-18

3,546 reads

Blogs

AI Step 1

By

As this is an Artificial Intelligence (AI) World, things are changing. We can see that...

Beginner’s Guide: Building a Dockerized Todo App with React, Chakra UI, and Rust for Backend

By

In a containerized app, React and Chakra UI provide a robust and accessible user...

A New Word: Nachlophobia

By

nachlophobia – n. the fear that your deepest connections with people are ultimately pretty...

Read the latest Blogs

Forums

Call dynamic sql storedprocedure from SSIS execute sql task

By komal145

hi, I have a table called Rules Create table Rules ( Id int ,...

Migrating database with many orphan users.

By JasonO

I am currently upgrading a very old database running SQL Server 2008 to SQL...

Active and Active Cluster

By shiv-356842

Hi Team, I am planning to apply security updates for SQL Server 2016 on...

Visit the forum

Question of the Day

The Funny SELECTs

What is returned from this query?

SELECT
  ( SELECT COUNT (*) FROM Sales.SalesOrderHeader AS soh
    WHERE soh.OrderDate >= '01/01/2011' AND soh.OrderDate < '01/01/2012') AS OrdersIn2011
, ( SELECT COUNT (*) FROM Sales.SalesOrderHeader AS soh
    WHERE soh.OrderDate >= '01/01/2012' AND soh.OrderDate < '01/01/2013') AS OrdersIn2012
, ( SELECT COUNT (*) FROM Sales.SalesOrderHeader AS soh
    WHERE soh.OrderDate >= '01/01/2013' AND soh.OrderDate < '01/01/2014') AS OrdersIn2013;

See possible answers