SQL Server Team-based Development - Red Gate Software

More documents

Recommendations

Info

Chapter 1: Writing Readable SQL Indenting Code without indenting is very difficult to follow. Indentation follows a very similar practice to a structured document, where the left margin is indented according to the nesting of the section heading. There should be a fixed number of spaces for each level of nesting. Generally, the use of tabs for indenting has resulted in indenting that is way too wide. Of course, written text can have wide indents, but it isn't done to around eight levels, skidding the text hard against the right-hand side of the page. Usually, two or three spaces is fine. It is at the point where we need to decide what comprises a change in the nesting level that things get difficult. We can be sure that, in a SELECT statement, all clauses are subordinate to the SELECT. Most of us choose to indent the FROM or the WHERE clause at the same level, but one usually sees the lists of columns indented. On the other hand, it is quite usual to see AND, ON, ORDER BY, OR, and so on, indented to the next level. What rules lie behind the current best practice? Many of us like to have one set of rules for DDL code, such as CREATE TABLE statements, and another for DML such as INSERT, UPDATE or SELECT statements. A CREATE TABLE statement, for example, will have a list of columns with quite a lot of information in them, and they are never nested, so indenting is likely to be less important than readability. You'd probably also want to insist on a new line after each column definition. The use of curly brackets in DDL also makes it likely that indenting will be used less. Formatting lists Lists occur all over the place in code. As in printed text, you can handle them in a number of different ways. If, for example, you are just listing entities, then you'd do it like this. I like many French cheeses, including Abbaye de Belloc, Baguette Laonnaise, Brie de 28
29 Chapter 1: Writing Readable SQL Melun, Calenzana, Crayeux de Roncq, Esbareich, Frinault, Mixte, Pavé du Berry, Port- Salut, Quercy Petit, Regal de la Dombes, Sainte Maure, Sourire Lozerien, Truffe, and Vignotte. Now, no typesetter would agree to arrange this in a vertical list, because the page would contain too much white space… I like many French cheeses, including: • Abbaye de Belloc • Baguette Laonnaise • Brie de Melun • Calenzana • Crayeux de Roncq • Esbareich • etc. …and they'd be most unlikely to want to put commas at the beginning of list elements. However, if the list elements consisted of longer strings, then it would be perfectly acceptable. In the same way, the rules for formatting SQL have to take into account the type of SQL statement being formatted, and the average length of each list element. Punctuation Commas, used as list separators, are often put at the beginning of lines. I realize that it makes the "commenting out" of list members easier during development, but it makes it difficult for those of us who are used to reading English text in books. Commas come at the end of phrases, with no space before them, but if they are followed by a word or phrase on the same line, then there is a space after the comma.
Page 1 and 2: The Red Gate Guide SQL Server Team-
Page 3 and 4: Copyright Phil Factor, Grant Fritch
Page 5 and 6: Publishing the Documentation ......
Page 7 and 8: Summary ...........................
Page 9: Huge,.many-parameter.stored.procedu
Page 12 and 13: developers, practicing agile develo
Page 14 and 15: Introduction Only small projects, r
Page 16 and 17: Introduction into a single reusable
Page 18 and 19: Chapter 1: Writing Readable SQL The
Page 20 and 21: Chapter 1: Writing Readable SQL Plu
Page 22 and 23: Chapter 1: Writing Readable SQL /*
Page 24 and 25: Chapter 1: Writing Readable SQL ( G
Page 26 and 27: Chapter 1: Writing Readable SQL •
Page 30 and 31: Chapter 1: Writing Readable SQL Sem
Page 34 and 35: Chapter 1: Writing Readable SQL INN
Page 38 and 39: Chapter 2: Documenting your Databas
Page 60 and 61: Chapter 3: Change Management and So
Page 78 and 79:
Chapter 3: Change Management and So
Page 80 and 81:
Page 82 and 83:
Page 84 and 85:
Page 86 and 87:
Page 88 and 89:
Page 90 and 91:
Page 92 and 93:
Page 94 and 95:
Page 96 and 97:
Chapter 4: Managing Deployments Fig
Page 98 and 99:
Chapter 4: Managing Deployments Aft
Page 100 and 101:
Chapter 4: Managing Deployments The
Page 102 and 103:
Chapter 4: Managing Deployments You
Page 104 and 105:
Chapter 4: Managing Deployments tf
Page 106 and 107:
Chapter 4: Managing Deployments Whi
Page 108 and 109:
Chapter 4: Managing Deployments dat
Page 110 and 111:
Chapter 4: Managing Deployments Fig
Page 112 and 113:
Chapter 4: Managing Deployments Thi
Page 114 and 115:
Chapter 4: Managing Deployments dep
Page 116 and 117:
Chapter 4: Managing Deployments Wha
Page 118 and 119:
Chapter 4: Managing Deployments Whe
Page 120 and 121:
Chapter 4: Managing Deployments Usi
Page 122 and 123:
Chapter 4: Managing Deployments How
Page 124 and 125:
Chapter 4: Managing Deployments Fun
Page 126 and 127:
Chapter 4: Managing Deployments Sum
Page 128 and 129:
Chapter 5: Testing Databases Why Te
Page 130 and 131:
Chapter 5: Testing Databases Black-
Page 132 and 133:
Chapter 5: Testing Databases I tend
Page 134 and 135:
Chapter 5: Testing Databases Error
Page 136 and 137:
Chapter 5: Testing Databases and st
Page 138 and 139:
Chapter 5: Testing Databases I take
Page 140 and 141:
Chapter 5: Testing Databases A test
Page 142 and 143:
Chapter 5: Testing Databases } } }
Page 144 and 145:
Chapter 5: Testing Databases QuickS
Page 146 and 147:
Chapter 5: Testing Databases } } }
Page 148 and 149:
Chapter 5: Testing Databases As a r
Page 150 and 151:
Chapter 5: Testing Databases Securi
Page 152 and 153:
Chapter 5: Testing Databases } dc =
Page 154 and 155:
Chapter 5: Testing Databases Listin
Page 156 and 157:
Chapter 5: Testing Databases Assert
Page 158 and 159:
Chapter 5: Testing Databases would
Page 160 and 161:
Chapter 5: Testing Databases Assert
Page 162 and 163:
Chapter 5: Testing Databases WHERE
Page 164 and 165:
Chapter 5: Testing Databases } Asse
Page 166 and 167:
Chapter 5: Testing Databases finall
Page 168 and 169:
Chapter 6: Reusing T-SQL Code It of
Page 170 and 171:
Chapter 6: Reusing T-SQL Code ) SEL
Page 172 and 173:
Chapter 6: Reusing T-SQL Code both
Page 174 and 175:
Chapter 6: Reusing T-SQL Code The c
Page 176 and 177:
Chapter 6: Reusing T-SQL Code CREAT
Page 178 and 179:
Chapter 6: Reusing T-SQL Code In fa
Page 180 and 181:
Chapter 6: Reusing T-SQL Code Hopef
Page 182 and 183:
Chapter 6: Reusing T-SQL Code Unfor
Page 184 and 185:
Chapter 6: Reusing T-SQL Code Whene
Page 186 and 187:
Chapter 6: Reusing T-SQL Code CREAT
Page 188 and 189:
Chapter 6: Reusing T-SQL Code Altho
Page 190 and 191:
Chapter 6: Reusing T-SQL Code Use c
Page 192 and 193:
Chapter 6: Reusing T-SQL Code Turn
Page 194 and 195:
Chapter 6: Reusing T-SQL Code -- ad
Page 196 and 197:
Chapter 6: Reusing T-SQL Code Name
Page 198 and 199:
Chapter 6: Reusing T-SQL Code Unfor
Page 200 and 201:
Chapter 7: Maintaining a Code Libra
Page 202 and 203:
Page 204 and 205:
Page 206 and 207:
Page 208 and 209:
Page 210 and 211:
Page 212 and 213:
Page 214 and 215:
Page 216 and 217:
Page 218 and 219:
Page 220 and 221:
Page 222 and 223:
Page 224 and 225:
Page 226 and 227:
Chapter 8: Exploring your Database
Page 228 and 229:
Page 230 and 231:
Page 232 and 233:
Page 234 and 235:
Page 236 and 237:
Page 238 and 239:
Page 240 and 241:
Page 242 and 243:
Page 244 and 245:
Page 246 and 247:
Page 248 and 249:
Page 250 and 251:
Page 252 and 253:
Page 254 and 255:
Page 256 and 257:
Page 258 and 259:
Page 260 and 261:
Chapter 9: Searching DDL and Build
Page 262 and 263:
Page 264 and 265:
Page 266 and 267:
Page 268 and 269:
Page 270 and 271:
Page 272 and 273:
Page 274 and 275:
Page 276 and 277:
Page 278 and 279:
Page 280 and 281:
Page 282 and 283:
Page 284 and 285:
Page 286 and 287:
Page 288 and 289:
Page 290 and 291:
Page 292 and 293:
Page 294 and 295:
Chapter 10: Automating CRUD If you
Page 296 and 297:
Chapter 10: Automating CRUD 'UNIQUE
Page 298 and 299:
Chapter 10: Automating CRUD Automat
Page 300 and 301:
Chapter 10: Automating CRUD LEFT OU
Page 302 and 303:
Chapter 10: Automating CRUD /* Huma
Page 304 and 305:
Chapter 10: Automating CRUD +'='+RE
Page 306 and 307:
Chapter 10: Automating CRUD So, we
Page 308 and 309:
Chapter 10: Automating CRUD Automat
Page 310 and 311:
Chapter 11: SQL Refactoring Code re
Page 312 and 313:
Chapter 11: SQL Refactoring SQL inj
Page 314 and 315:
Chapter 11: SQL Refactoring For a c
Page 316 and 317:
Chapter 11: SQL Refactoring ORDER B
Page 318 and 319:
Chapter 11: SQL Refactoring However
Page 320 and 321:
Chapter 11: SQL Refactoring ) SELEC
Page 322 and 323:
Chapter 11: SQL Refactoring same as
Page 324 and 325:
Chapter 11: SQL Refactoring Table '
Page 326 and 327:
Chapter 11: SQL Refactoring - - Cre
Page 328 and 329:
Chapter 11: SQL Refactoring - - cre
Page 330 and 331:
Chapter 11: SQL Refactoring auditin
Page 332 and 333:
Chapter 11: SQL Refactoring The res
Page 334 and 335:
Chapter 11: SQL Refactoring /* This
Page 336 and 337:
Chapter 11: SQL Refactoring DECLARE
Page 338 and 339:
Chapter 11: SQL Refactoring THEN RI
Page 340 and 341:
Chapter 11: SQL Refactoring FOR SEL
Page 342 and 343:
Chapter 11: SQL Refactoring FROM ma
Page 344 and 345:
Chapter 11: SQL Refactoring give in
Page 346 and 347:
Chapter 11: SQL Refactoring /* The
Page 348 and 349:
Chapter 11: SQL Refactoring world,
Page 350 and 351:
SQL Compare ® Pro Compare and sync
Page 352 and 353:
Deployment Manager Automated deploy
Page 354 and 355:
SQL Monitor from $795 SQL Server pe
Page 356 and 357:
You can buy our acclaimed SQL Serve
Page 358 and 359:
.NET Reflector Decompile, debug, an
Page 360:
The Red Gate Guides SQL Server Back
show all

SQL Server Team-based Development - Red Gate Software

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?