The Art of SQL Server FILESTREAM - Red Gate Software

More documents

Recommendations

Info

Chapter 8: Backup and Restore for FILESTREAM DatabasesOur complete backup scheme for the NorthPole database consists of a full backup, adifferential backup and two transaction log backups. With these backup files, we couldperform another restore operation to completely restore the NorthPole database;in other words, we could restore each backup file in sequence, rolling the databaseforward to the state it existed in at the end of the second log backup, and then recoverthe database. In fact, in this very simple case, we can perform a complete restore simplyusing the full backup and the two transaction log backups; remember that a log backupcaptures all contents in the log file since the last log backup and so, in this case, the firsttransaction log backup will contain the log records for both the rows added after the fullbackup, and the second log backup will contain the details of the final insert. In a morerealistic backup scheme, there would likely have been transaction log backups taken atregular intervals in the time between the full backup and the differential backup. In sucha case, the differential backup would have allowed us to avoid having to restore thoselog backups, and our restore operation would instead have used just the full backup, thedifferential backup, and any subsequent log backups.In any event, the problem we have here is that a complete restore would return thedatabase to the state where the contents of the Items table were deleted since, when werestore the second log backup, it would roll forward, not only the fourth insert, but alsothe transaction that deleted the contents of Items. What we want to do instead, to getall the contents of our Items table back, is restore to a specific point in time within thatsecond log backup; namely, the time that we recorded after the fourth insert, but beforethe accidental delete.Fortunately, SQL Server supports point-in-time recovery of FILESTREAM databases;when you restore a FILESTREAM-enabled database from a certain point in time, theFILESTREAM data will be consistent with the relational data in the restored database.Let's look at an example that performs a point-in-time restore of a FILESTREAMdatabase. This time, instead of restoring over the top of the existing NorthPoledatabase, we're going to restore to a new database, called NothPole2. At the end of thisoperation what we should have is a NorthPole database, with one row in the Itemstable, and a NorthPole2 database with all four rows back in the Items table.320
Chapter 8: Backup and Restore for FILESTREAM DatabasesThe first step is to restore the full backup to create the NorthPole2 database, as shownin Listing 8-7. Notice the use of the NORECOVERY option; this instructs SQL Server toleave the database in a restoring state, ready to receive more backup files.-- Restore the full backupRESTORE DATABASE NorthPole2FROM DISK = 'C:\ArtOfFS\Demos\Chapter8\bak\NorthPole.bak'WITH NORECOVERY,MOVE 'NorthPole' TO 'C:\ArtOfFS\Demos\Chapter8\NorthPole2.mdf',MOVE 'NorthPole_log' TO 'C:\ArtOfFS\Demos\Chapter8\NorthPole2_log.ldf',MOVE 'NorthPole_fs' TO 'C:\ArtOfFS\Demos\Chapter8\NorthPole2_fs',GOListing 8-7:Restoring a full backup.The code uses the MOVE option three times, to specify the location of the data file,log file, and FILESTREAM data container, respectively. Note that the leaf-level folder(NorthPole2_fs in this example) should not exist already, but the containing folder(C:\ArtOfFS\Demos\Chapter8) must exist! SQL Server reserves the "exclusive" rightsto create and configure NorthPole2_fs folder as part of the restore operation.The next step is to completely restore the first transaction log backup, again leaving theNorthPole2 database in a restoring state.RESTORE LOG NorthPole2FROM DISK = 'C:\ArtOfFS\Demos\Chapter8\bak\NorthPole_log.trn'WITH NORECOVERYListing 8-8:Restoring the transaction log backup.The final step is the interesting one; we apply the second log backup, but stop the restoreat the point just before the data was accidentally deleted, and then recover the database.If you are following this example on your own system, insert the date and time fromListing 8-9.321
Page 1 and 2:
DBA HandbooksThe Art ofSQL Server F
Page 3 and 4:
Copyright June 2012ISBN 978-1-90643
Page 5 and 6:
Updating and deleting FILESTREAM da
Page 7 and 8:
Creating the stored procedure to fe
Page 9 and 10:
File Backups and Piecemeal Restores
Page 11 and 12:
Setting Up the Server for FileTable
Page 13 and 14:
Using SSMS to check that FILESTREAM
Page 15 and 16:
Sven AeltermanSven Aelterman is a l
Page 17 and 18:
Finding time for writing such a len
Page 19 and 20:
IntroductionWhen I first started my
Page 21 and 22:
The secondary audience for this boo
Page 23 and 24:
Chapter 1: Storing and ManagingUnst
Page 25 and 26:
Chapter 1: Storing and Managing Uns
Page 27 and 28:
Page 29 and 30:
Page 31 and 32:
Page 33 and 34:
Page 35 and 36:
Page 37 and 38:
Page 39 and 40:
Page 41 and 42:
Setting the access levelChapter 1:
Page 43 and 44:
Page 45 and 46:
Data usage patternsChapter 1: Stori
Page 47 and 48:
Page 49 and 50:
Chapter 2: Getting Started with FIL
Page 51 and 52:
Page 53 and 54:
Page 55 and 56:
Page 57 and 58:
Page 59 and 60:
Page 61 and 62:
Page 63 and 64:
Page 65 and 66:
Page 67 and 68:
Page 69 and 70:
Page 71 and 72:
Page 73 and 74:
Page 75 and 76:
Page 77 and 78:
Page 79 and 80:
Page 81 and 82:
Page 83 and 84:
Page 85 and 86:
Page 87 and 88:
Page 89 and 90:
Chapter 3: Accessing FILESTREAMData
Page 91 and 92:
Chapter 3: Accessing FILESTREAM Dat
Page 93 and 94:
Page 95 and 96:
Page 97 and 98:
Page 99 and 100:
Page 101 and 102:
Page 103 and 104:
Page 105 and 106:
Page 107 and 108:
Page 109 and 110:
Page 111 and 112:
Page 113 and 114:
Page 115 and 116:
Page 117 and 118:
Page 119 and 120:
Page 121 and 122:
Page 123 and 124:
Page 125 and 126:
Page 127 and 128:
Page 129 and 130:
Page 131 and 132:
Chapter 4: FILESTREAM with EntityFr
Page 133 and 134:
Chapter 4: FILESTREAM with Entity F
Page 135 and 136:
Page 137 and 138:
Page 139 and 140:
Page 141 and 142:
Page 143 and 144:
Page 145 and 146:
Page 147 and 148:
Page 149 and 150:
Page 151 and 152:
Page 153 and 154:
Page 155 and 156:
Page 157 and 158:
Page 159 and 160:
Page 161 and 162:
Page 163 and 164:
Page 165 and 166:
Chapter 5: FILESTREAM with ASP.NETa
Page 167 and 168:
Chapter 5: FILESTREAM with ASP.NET
Page 169 and 170:
Page 171 and 172:
Page 173 and 174:
Page 175 and 176:
Page 177 and 178:
Page 179 and 180:
Page 181 and 182:
Page 183 and 184:
Page 185 and 186:
Page 187 and 188:
Page 189 and 190:
Page 191 and 192:
Page 193 and 194:
Page 195 and 196:
Page 197 and 198:
Page 199 and 200:
Page 201 and 202:
Page 203 and 204:
Page 205 and 206:
Page 207 and 208:
Page 209 and 210:
Page 211 and 212:
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:
Chapter 6: FILESTREAM with SSIS and
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:
Page 257 and 258:
Page 259 and 260:
Page 261 and 262:
Page 263 and 264:
Creating a data sourceChapter 6: FI
Page 265 and 266:
Page 267 and 268:
Page 269 and 270: Chapter 6: FILESTREAM with SSIS and
Page 271 and 272: Chapter 7: FILESTREAM Database Admi
Page 289 and 290: Fixing corrupted dataChapter 7: FIL
Page 313 and 314: Chapter 8: Backup and Restore for F
Page 319: Chapter 8: Backup and Restore for F
Page 329 and 330: Chapter 9: Investigating FILESTREAM
Page 351 and 352: Chapter 10: Integrating FILESTREAMw
Page 353 and 354: Chapter 10: Integrating FILESTREAM
Page 371 and 372:
Chapter 10: Integrating FILESTREAM
Page 373 and 374:
Page 375 and 376:
Page 377 and 378:
Page 379 and 380:
Page 381 and 382:
Page 383 and 384:
Page 385 and 386:
Page 387 and 388:
Chapter 11: FileTableThe addition o
Page 389 and 390:
Chapter 11: FileTableColumn Namestr
Page 391 and 392:
Chapter 11: FileTableColumn Nameis_
Page 393 and 394:
Chapter 11: FileTableUSE NorthPoleG
Page 395 and 396:
Chapter 11: FileTableMore on using
Page 397 and 398:
Chapter 11: FileTableFigure 11-1:Se
Page 399 and 400:
Chapter 11: FileTableperformance wh
Page 401 and 402:
Chapter 11: FileTableany files or f
Page 403 and 404:
Chapter 11: FileTable-- If the 'Nor
Page 405 and 406:
Chapter 11: FileTableBy default, th
Page 407 and 408:
Chapter 11: FileTableIt is possible
Page 409 and 410:
Chapter 11: FileTableFigure 11-4:Ch
Page 411 and 412:
Chapter 11: FileTableFurthermore, i
Page 413 and 414:
Chapter 11: FileTableCreating folde
Page 415 and 416:
Chapter 11: FileTableAdding rows us
Page 417 and 418:
Chapter 11: FileTable-- Find the pa
Page 419 and 420:
Chapter 11: FileTable-- Insert a ne
Page 421 and 422:
Chapter 11: FileTablestring SqlText
Page 423 and 424:
Chapter 11: FileTableAs a best prac
Page 425 and 426:
Chapter 11: FileTableSELECT file_st
Page 427 and 428:
Chapter 11: FileTable• non_transa
Page 429 and 430:
Chapter 11: FileTable• filename_c
Page 431 and 432:
Chapter 11: FileTableListing 11-29
Page 433 and 434:
Chapter 11: FileTableLanguage suppo
Page 435 and 436:
Chapter 11: FileTableInvestigating
Page 437 and 438:
Chapter 12: Planning, Configuration
Page 439 and 440:
Page 441 and 442:
Page 443 and 444:
Page 445 and 446:
Page 447 and 448:
Page 449 and 450:
Page 451 and 452:
Page 453 and 454:
Page 455 and 456:
Page 457 and 458:
Page 459 and 460:
Appendix A: Configuring FILESTREAMo
Page 461 and 462:
Appendix A: Configuring FILESTREAM
Page 463 and 464:
Page 465 and 466:
Page 467 and 468:
Page 469 and 470:
Page 471 and 472:
Page 473 and 474:
Page 475 and 476:
Page 477 and 478:
Page 479 and 480:
Page 481 and 482:
Page 483 and 484:
Page 485 and 486:
Page 487:
About Red GateYou know those annoyi
show all

The Art of SQL Server FILESTREAM - Red Gate Software

Create successful ePaper yourself

Delete template?

Save as template?