The Red Gate Guide to SQL Server Team-based Development

Mladen Prajdic, Grant Fritchey, Alex Kuznetsov, "The Red Gate Guide to SQL Server Team-based Development"
Red Gate Books | 2010 | ISBN: 190643459X | 374 pages | PDF | 7,1 MB
This book shows how to use of mixture of home-grown scripts, native SQL Server tools, and tools from the Red Gate SQL Toolbelt, to successfully develop database applications in a team environment, and make database development as similar as possible to "normal" development.

View the original article here

Defensive Database Programming with SQL Server

Defensive Database Programming with SQL Server
R*d G*te Books | 2010 | ISBN: 190643445X | 291 pages | PDF | 2,6 MB
Resilient T-SQL code is code that is designed to last, and to be safely reused by others. The goal of defensive database programming, the goal of this book, is to help you to produce resilient T-SQL code that robustly and gracefully handles cases of unintended use, and is resilient to common changes to the database environment. Too often as developers, we stop work as soon as our code passes a few basic tests to confirm that it produces the 'right result' in a given use case. We do not stop to consider what other possible ways in which the code might be used in the future, or how our code will respond to common changes to the database environment, such as a change in the database language setting, or a change to the nullability of a table column, and so on

Download Hotfile.com
http://hotfile.com/dl/88751910/696028a/Database_SQL.rar.html

View the original article here

Defensive Database Programming with SQL Server

Alex Kuznetsov, "Defensive Database Programming with SQL Server"
R*d G*te Books | 2010 | ISBN: 190643445X | 291 pages | PDF | 2,6 MB
Resilient T-SQL code is code that is designed to last, and to be safely reused by others. The goal of defensive database programming, the goal of this book, is to help you to produce resilient T-SQL code that robustly and gracefully handles cases of unintended use, and is resilient to common changes to the database environment. Too often as developers, we stop work as soon as our code passes a few basic tests to confirm that it produces the 'right result' in a given use case. We do not stop to consider what other possible ways in which the code might be used in the future, or how our code will respond to common changes to the database environment, such as a change in the database language setting, or a change to the nullability of a table column, and so on. In the short-term, this approach is attractive; we get things done faster. However, if our code is designed to be used for more than just a few months, then it is very likely that such changes can and will occur, and the inevitable result is broken code or, even worse, code that silently starts to behave differently, or produce different results. When this happens, the integrity of our data is threatened, as is the validity of the reports on which critical business decisions are often based. At this point, months or years later, and long after the original developer has left, begins the painstaking process of troubleshooting and fixing the problem. Would it not be easier to prevent all this troubleshooting from happening? Would it not be better to spend a little more time and effort during original development, to save considerably more time on troubleshooting, bug fixing, retesting, and redeploying? This is what defensive programming is all about: we learn what can go wrong with our code, and we proactively apply this knowledge during development. This book is filled with practical, realistic examples of the sorts of problems that beset database programs, including: - Changes in database objects, such as tables, constraints, columns, and stored procedures. - Changes to concurrency and isolation levels. - Upgrades to new versions of SQL Server. - Changes in requirements. - Code reuse. - Problems causing loss of data integrity. - Problems with error handling in T-SQL. In each case, it demonstrates approaches that will help you understand and enforce (or eliminate) the assumptions on which your solution is based, and to improve its robustness. Ultimately, the book teaches you how to think and develop defensively, and how to proactively identify and eliminate potential vulnerabilities in T-SQL code.

View the original article here

IBM InfoSphere Replication Server and Data Event Publisher

IBM InfoSphere Replication Server and Data Event Publisher
Publisher: Packt | 2010 | PDF | 334 pages | ISBN: 1849681546 | 7 Mb
Design, implement, and monitor a successful Q replication and Event Publishing project

* Covers the toolsets needed to implement a successful Q replication project
* Aimed at the Linux, Unix, and Windows operating systems, with many concepts common to z/OS as well
* A chapter dedicated exclusively to WebSphere MQ for the DB2 DBA
* Detailed step-by-step instructions for 13 Q replication scenarios with troubleshooting and monitoring tips
* Written in a conversational and easy to follow manner

In Detail

Business planning is no longer just about defining goals, analyzing critical issues, and then creating strategies. You must aid business integration by linking changed-data events in DB2 databases on Linux, UNIX, and Windows with EAI solutions , message brokers, data transformation tools, and more. Investing in this book will save you many hours of work (and heartache) as it guides you around the many potential pitfalls to a successful conclusion.

This book will accompany you throughout your Q replication journey. Compiled from many of author's successful projects, the book will bring you some of the best practices to implement your project smoothly and within time scales. The book has in-depth coverage of Event Publisher, which publishes changed-data events that can run updated data into crucial applications, assisting your business integration processes. Event Publisher also eliminates the hand coding typically required to detect DB2 data changes that are made by operational applications.

We start with a brief discussion on what replication is and the Q replication release currently available in the market. We then go on to explore the world of Q replication in more depth. The latter chapters cover all the Q replication components and then talk about the different layers that need to be implemented-the DB2 database layer, the WebSphere MQ layer, and the Q replication layer. We conclude with a chapter on how to troubleshoot a problem. The Appendix (available online) demonstrates the implementation of 13 real-time Q replication scenarios with step-by-step instructions.

Publish changed data events in order to operate updated data into critical applications, thus helping your business integration processes with this professional guide

What you will learn from this book

* Use Q replication to feed a data warehouse and explore the way it interacts with the DB2 High Availability Disaster Recovery (HADR) function
* Master the main phases of the DB2 database layer, the WebSphere layer, and the Q replication layer, which make up a Q replication solution
* Create and configure the control tables required by Q replication, and quickly examine how the Q replication components communicate from a DB2 perspective
* Set up a Q replication and Event Publishing environment
* Administer a Q replication and Event Publishing environment
* Troubleshoot an existing Q replication and Event Publishing environment
* Implement 13 Q replication scenarios, ranging from the unidirectional replication to peer-to-peer, with step-by-step instructions

Download Links

http://hotfile.com/dl/88499073/1a96dd6/1849681546.rar.html
http://www.fileserve.com/file/tWjydYt/1849681546.rar

View the original article here