System Development Life Cycle

External Article

SQL database control and deployment

  • Article

If you develop SQL databases, you know how difficult it can be to promote from the development environment to production with any level of confidence that the databases are the same.

When you have upgrades, it’s difficult to identify changes as well, especially when there are multiple developers making changes to multiple databases. The problem is compounded if your target environment is a client’s system over which you have no control. It’s staggering to think about what can happen if there are 600-plus client systems that have various versions of your database.

2005-09-06

2,677 reads

SQLServerCentral Article

Administering a Development Environment

  • Article

In any well run development environment, you will have a separate SQL Server for developers to work on, completely different from your production server. However there are a few tricks that Jason Hall brings us that you might want to implement to ensure a smooth running environment.

1.5 (2)

2005-08-09

7,563 reads

Technical Article

Using Source Control to Develop Smarter

  • Article

Veteran and novice developers alike need source control management (SCM). Also known as asset management, and source code management, SCM helps you (and your team) manage development projects, and the components and code that make up the project.

There are many benefits to using source control management, most notably the ability to develop code faster, smarter and more accurately. Source control management tools help you control your code; especially in multiple developer projects.

2005-03-29

2,049 reads

Technical Article

The Trustworthy Computing Security Development Lifecycle

  • Article

This paper discusses the Trustworthy Computing Security Development Lifecycle (or SDL), a process that Microsoft has adopted for the development of software that needs to withstand malicious attack. The process encompasses the addition of a series of security-focused activities and deliverables to each of the phases of Microsoft's software development process. These activities and deliverables include the development of threat models during software design, the use of static analysis code-scanning tools during implementation, and the conduct of code reviews and security testing during a focused "security push". Before software subject to the SDL can be released, it must undergo a Final Security Review by a team independent from its development group. When compared to software that has not been subject to the SDL, software that has undergone the SDL has experienced a significantly reduced rate of external discovery of security vulnerabilities. This paper describes the SDL and discusses experience with its implementation across Microsoft software.

2005-03-28

1,230 reads

Blogs

Daily Coping 5 Aug 2022

By

I started to add a daily coping tip to the SQLServerCentral newsletter and to...

Daily Coping 4 Aug 2022

By

I started to add a daily coping tip to the SQLServerCentral newsletter and to...

What’s next III

By

In case you didn’t know I was given notice about a month and a...

Read the latest Blogs

Forums

Which version of SSMS to connect to SSIS 2008

By planetmatt

I suspect that an SSIS package in source control is not the latest deployed...

Use 2 CTEs in a Single SQL Query

By gjoelson 29755

Hi , I'm trying to union 2 CTE queries into one.  but must be...

Business Analytics from Application Logs and SQL Server Database using Splunk

By roopesh.uniyal@gmail.com

Comments posted to this topic are about the item Business Analytics from Application Logs...

Visit the forum

Ask SSC Logo Ask SSC

SQL Server Q&A from the SQLServerCentral community

Get answers

Question of the Day

DATETRUNC

See possible answers