Advertisement
Published in:
2009 | OriginalPaper | Chapter
Planning and Installing SQL Server 2008
Authors : Robert E. Walters, Grant Fritchey, Carmen Taglienti
Published in: Beginning SQL Server 2008 Administration
Publisher: Apress
Activate our intelligent search to find suitable subject content or patents.
Select sections of text to find matching patents with Artificial Intelligence. powered by
Select sections of text to find additional relevant content using AI-assisted search. powered by
For some reason during my time as an application development consultant, I ended up working on a few projects where I was writing an InstallShield or Windows Installer package for the client. As a former developer working in various environments, I have made my own hypothesis that, in general, whoever gets stuck writing install scripts must feel like the little kid who got picked last for a kickball team in fifth grade. There is nothing glamorous about setup. The only time your code is being run is when the application is installed, updated, or removed. So if my hypothesis is correct and writing setup scripts is not the most exciting task for developers, then one can assume that, in general, the overall experience to the end user might not be optimal. After all, as a developer, why should you put much effort in something that is going to run only a few times in the life of the product?