Books by Tony Davis

Few software developers would build an application without using source control, but its adoption for databases has been slower. Yet without source control to maintain the scripts necessary to create our database objects, load lookup data, and take other actions, we cannot guarantee a reliable and repeatable database deployment process, let alone coordinate database upgrades with changes to the application. We also run the risk that our "ad hoc" database patching will cause inconsistencies and data loss. Source control can and should play a key role in the database development and deployment process, and this book will show you exactly how to get started. It provides 'just enough' detail about the core components of a source control system and how to incorporate that system into the database development and deployment processes, covering: - Database Source Control architecture - what to include, how to structure the components - Collaborative editing - teamwork on a database project, while minimizing change conflicts and data loss. - Change auditing - what changed between versions and who changed it? - Branching -work independently on separate features and control what to deploy and when - Merging - what happens if one user changes a column name while another updates its data type? A merge operation lets the team decide the correct outcome - Building and Deploying databases - building new databases and upgrading existing ones from source control Every chapter follows the same "half-theory, half practice" template, so you learn the concepts then see how they work.

When a SQL Server database is operating smoothly and performing well, there is no need to be particularly aware of the transaction log, beyond ensuring that every database has an appropriate backup regime and restore plan in place. When things go wrong, however, a DBA's reputation depends on a deeper understanding of the transaction log, both what it does, and how it works. An effective response to a crisis requires rapid decisions based on understanding its role in ensuring data integrity.

Talented and ambitious people will only stay with their current employer if they are offered positive development, motivation and nurturing to ensure they are given every chance of realizing their potential. This book shows how to manage the needs of the individual employees and those of the organization in parallel.

Traditionelt er projektledere blevet tildelt et projekt, og deres rolle har været at levere til tiden, i henhold til aftalt kvalitet og inden for budgettet. I bagklogskabens lys erkender kunden imidlertid ofte først, hvad han reelt ønsker, når projektet er leveret, og da er der ofte en kløft mellem forventningerne og det færdige produkt. Projektledelse er under forandring, og den samlede indvirkning på virksomheden skal håndteres på en mere effektiv måde - og her kommer relationship manageren ind i billedet.Relationship managerens sande rolle er identisk med orkesterdirigentens. Det er hans opgave ...- at tage kontakt til kunden og skaffe sig forståelse for kundens korte, mellemlange og langsigtede mål- at omforme det på en måde, som projektteamet kan håndtere- at modtage en specifikation fra projektteamet over det arbejde, der skal udføres, inklusive planer, vurderinger og oversigter samt detaljerede analysestrukturer for arbejde og omkostninger for at tjekke, at de virkelig har forstået, hvad der skal gøres og af hvem. Først når relationship manageren er tilfreds, vender han tilbage til kunden for at sælge VÆRDI.Relationship manageren er skrevet for at udfylde kløften mellem de tekniske og forretningsmæssige aspekter for succesfuld aflevering af et projekt. Der gives praktiske retningslinjer for, hvordan denne nye måde kan virkeliggøres, og der opstilles detaljer for kompetencer og teknikker, der er nødvendige for at få succes inden for den nyeste udvikling i projektledelse.