Continuous Integration
Continuous Integration is a popular process where software is developed incrementally, and each increment is integrated into the package as a whole. You’ll find this techniques used for many different software development lifecycles because it is not constrained to a specific flow. The only constraint is that as each incremental software aspect is completed it is rolled into the current package.
I enjoy working in environments where continuous integration is automated. In a development environment it is integrated with each version control check in. In a QA environment software is integrated when completed in Dev. In the production packaging environment, software is integrated when it passes QA requirements.
Continuous integration doesn’t just happen. It requires some thought when developing software. SOLID principles become important when doing continuous integration. For example, the Open/Closed principle is important to follow with continuous integration. A Class is open for extension, but closed for modification. Following Open/Closed means you extend existing classes so that they can continue to work as previously released, while allowing new capabilities to be added. In this fashion, continuous integration doesn’t require all new features to be completely implemented in order for integration because the older code continues to work.
Why not share your experience with Continuous integration? Write to btaylor@sswug.org with the challenges you have faced, changes you have made to your processes, or even tools or principles you have found useful for Continuous Integration.
Reader Response – Database Monitoring
John Writes:
I currently have a SSIS running a query on table sizes that saves the results to a table on another then mails the.
I also have a Powershell script that (I haven’t wired this up for mail delivery………….yet):
- Sweeps both sql logs and events logs on all servers
- Combines them into one uniform file so I can see the SQL and Eventlogs in a "stream of time" type of format
- Checks the log space and memory utilization
Cheers,
Ben
$$SWYNK$$
Featured Article(s)
Database Snapshots – A View of Database at a Specific Point in Time
Beginning with SQL Server 2005, Microsoft introduced a new feature called database snaphots, which gives DBAs a way of presenting a consistent view of data at a certain time. So in other words we can say that it is a static, read-only copy of a source database that gives you a consistent view of a database as of a certain point in time. You can use the snapshot for operations supported by a read-only database, such as reporting applications. You can create multiple database snapshots on a source database. You can recover the source database to the point when the snapshot was created from a database snapshot. However, when recovering from a snapshot, the source database must be available.
Featured White Paper(s)
Go Beyond SCOM Monitoring with Foglight for SQL Server
read more)