Defensive Database Programming - Red Gate Software

More documents

Recommendations

Info

Chapter 4: When Upgrading Breaks CodeINSERT INTO dbo.Developers(DeveloperID,FirstName,Lastname,Status)SELECT 1,'Arnie','Brown','Active'UNION ALLSELECT 2,'Carol','Dale','Active' ;GOINSERT INTO dbo.Tickets(TicketID,AssignedToDeveloperID,Description,Status)SELECT 1,1,'Order entry form blows up','Active'UNION ALLSELECT 2,2,'Incorrect totals in monthly report','Closed' ;Listing 4-11: Adding test data to the Developers and Tickets tables.114
Chapter 4: When Upgrading Breaks CodeOur test data includes one developer (Arnie) who is currently active and has one activeticket assigned to him, so we can test what happens if Arnie attempts to go on holidaywithout assigning his ticket to someone else. Apparently, under READ COMMITTEDisolation level, our Developers_Upd trigger prevents violation of this business rule, asshown in Listing 4-12.SET TRANSACTION ISOLATION LEVEL READ COMMITTED ;UPDATE dbo.DevelopersSET Status = 'Vacation'WHERE DeveloperID = 1 ;Msg 50000, Level 16, State 1, Procedure Developers_Upd, Line11Developers must assign their active tickets to someone elsebefore going on vacationMsg 3609, Level 16, State 1, Line 2The transaction ended in the trigger. The batch has beenaborted.Listing 4-12: Testing the Developers_Upd trigger.Similarly, our dbo.Tickets_Upd trigger ensures that inactive tickets cannot bechanged to active status if they are assigned to developers who are on vacation, as shownin Listing 4-13.SET TRANSACTION ISOLATION LEVEL READ COMMITTED ;-- make sure Carol's ticket is closedUPDATE dbo.TicketsSET Status = 'Closed'WHERE TicketID = 2 ;-- Carol can now go on vacationUPDATE dbo.DevelopersSET Status = 'Vacation'WHERE DeveloperID = 2 ;115
Page 5 and 6:
Chapter 2: Code Vulnerabilities due
Page 7 and 8:
Enforcing Data Integrity in the App
Page 9 and 10:
About the AuthorAlex Kuznetsov has
Page 11 and 12:
IntroductionResilient T-SQL code is
Page 13 and 14:
IntroductionCh. 02: Code Vulnerabil
Page 15 and 16:
IntroductionSpecific examples demon
Page 17:
IntroductionWhat this book does not
Page 21 and 22:
Chapter 1: Basic Defensive Database
Page 24 and 25:
Page 26 and 27:
Page 28 and 29:
Page 30 and 31:
Page 32 and 33:
Page 34 and 35:
Page 36 and 37:
Page 38 and 39:
Page 40 and 41:
Page 42 and 43:
Page 44 and 45:
Page 46 and 47:
Page 48 and 49:
Page 50 and 51:
Page 52 and 53:
Page 54 and 55:
Page 57 and 58:
Chapter 2: Code Vulnerabilitiesdue
Page 59 and 60:
Page 61 and 62:
Page 63 and 64: Chapter 2: Code Vulnerabilities due
Page 75: Chapter 2: Code Vulnerabilities due
Page 78 and 79: Chapter 3: Surviving Changes to Dat
Page 104 and 105: 104
Page 106: Chapter 4: When Upgrading Breaks Co
Page 109 and 110: Chapter 4: When Upgrading Breaks Co
Page 113: Chapter 4: When Upgrading Breaks Co
Page 132 and 133: Chapter 5: Reusing T-SQL CodeThe Da
Page 134 and 135: Chapter 5: Reusing T-SQL CodeIt is
Page 136 and 137: Chapter 5: Reusing T-SQL CodeAverag
Page 138 and 139: Chapter 5: Reusing T-SQL CodeBEGINS
Page 140 and 141: Chapter 5: Reusing T-SQL CodeWe als
Page 142 and 143: Chapter 5: Reusing T-SQL CodeLet's
Page 144 and 145: Chapter 5: Reusing T-SQL CodeStateC
Page 146 and 147: Chapter 5: Reusing T-SQL CodeStateC
Page 148 and 149: Chapter 5: Reusing T-SQL CodeBEGIN
Page 150 and 151: Chapter 5: Reusing T-SQL CodeSELECT
Page 152 and 153: Chapter 5: Reusing T-SQL CodeReusin
Page 154 and 155: Chapter 5: Reusing T-SQL CodeIt is
Page 156 and 157: Chapter 5: Reusing T-SQL CodeINSERT
Page 158 and 159: Chapter 5: Reusing T-SQL CodeListin
Page 160 and 161: Chapter 5: Reusing T-SQL CodeUnique
Page 162 and 163: 162
Page 164 and 165:
Chapter 6: Common Problems with Dat
Page 166 and 167:
Page 168 and 169:
Page 170 and 171:
Page 172 and 173:
Page 174 and 175:
Page 176 and 177:
Page 178 and 179:
Page 180 and 181:
Page 182 and 183:
Page 184 and 185:
Page 186 and 187:
Page 188 and 189:
Page 190 and 191:
Page 192 and 193:
Page 194 and 195:
Page 196 and 197:
Page 198 and 199:
Page 200 and 201:
Page 202 and 203:
Page 205 and 206:
Page 207 and 208:
Page 209 and 210:
Chapter 7: Advanced Use ofConstrain
Page 211 and 212:
Chapter 7: Advanced Use of Constrai
Page 213 and 214:
Page 215 and 216:
Page 217 and 218:
Page 219 and 220:
Page 221 and 222:
Page 223 and 224:
Page 225 and 226:
Page 227 and 228:
Page 229 and 230:
Page 231 and 232:
Page 233 and 234:
Page 235 and 236:
Page 237 and 238:
Page 239 and 240:
Page 241 and 242:
Page 243 and 244:
Page 245 and 246:
Page 247 and 248:
Page 249 and 250:
Page 251 and 252:
Page 253 and 254:
Page 255 and 256:
Chapter 8: Defensive ErrorHandlingT
Page 257 and 258:
Chapter 8: Defensive Error Handling
Page 259 and 260:
Page 261 and 262:
Page 263 and 264:
Page 265 and 266:
Page 267 and 268:
Page 269 and 270:
Page 271 and 272:
Page 273 and 274:
Page 275 and 276:
Page 277 and 278:
Page 279 and 280:
Page 281 and 282:
Page 283 and 284:
Page 285 and 286:
Page 287 and 288:
Page 289 and 290:
Page 291 and 292:
show all

Defensive Database Programming - Red Gate Software

Create successful ePaper yourself

Delete template?

Save as template?