Yesterday, I
gave a presentation at the “Israeli SQL Server User Group”
(Part of PASS), discussing the importance of continuous integration, automatic
build, and the approach of SQL Code handling in general.
Lecturing
there was a pleasure, the audience was great and I’ve got many responses during,
and after the presentation.
Presentation
aside; what puzzles me the most, is the fact that many SQL Developers don’t
treat their code the way other developers (c#, java etc...) do
SQL Code is
not just ad-hoc scripts; the code is often part of a big enterprise system -
It has to
connect altogether, to compile & build, to use the right references and to
be clean and readable.
Keeping
these guidelines, even before you implement Automatic builds / CI, help you be
in control when a team of SQL developers rapidly write new code and modify
existing one.
Another
thing worth mentioning is – Automatic deployment in Visual Studio is by all
means, not intended for production deployment.
The main
concept is to keep an updated, high-quality development (and maybe QA)
environments with the latest code. This will help us:
- Provide a ‘Latest’ database version for integration with the other dev teams
- Ensure code quality and stability
For
production, use whatever you like (diff scripts, 3rd parties…)
 |
| "Bad Code" |
So, there
are many solutions out there. I’ve used Unified Remote (for Android) along with
the server-side installation
Control can
be done either through Wi-Fi or BT
get it here:
