لطفا منتظر باشید ...
Chapter 1. Stored Procedure Primer
Today, average software development practices are becalmed in a windless sea of code-and-fix programminga kind of flat-earth approach to software development that was proven ineffective 20 years ago.
Steve McConnell[1]
[1] McConnell, Steve. After the Gold Rush. Redmond, WA: Microsoft Press, 1998. Page 91.
Working from the assumption that the human brain learns by associating new data with what it already knows, we'll spend this chapter building a base framework onto which we can assemble the knowledge conveyed by the remainder of the book. We'll touch on the topics covered in the book's other chapters, but we'll save the details for the chapters themselves. I'm assuming that you know some basic Transact-SQL with which we can associate these high-level concepts. We'll spend the remainder of the book filling in the details and expanding on what we cover here.
This chapter serves to prime the discussion on SQL Server stored procedure programming. It will tell you what a stored procedure is, how stored procedures are often used, and why and how you should use them. It will also jumpstart the treatment of Transact-SQL as a full-fledged programming language. If I could have you take one thing away from reading this book, it would be that Transact-SQL programming is very much like any other type of programming: It requires the same attention to detail, the same craftsmanship, and the same software engineering skill to do well.
