SQL SERVER 2008

Recommendations

Info

482 ❘ CHAPTER 17 RUNNING SQL SERVER IN A VIRTUAL ENVIRONMENT Virtual Server (or Guest Server or Virtual Machine) The running of virtual servers, also called guest servers or virtual machines, is the sole purpose of a virtual environment. Each virtual server has very similar properties to a traditional physical server in that it will have a number of virtual CPUs, an amount of memory, and a quantity of virtual hard drives assigned to it. “Inside” the guest server, a regular operating system such as Windows Server 2008 will be installed on drive C: — just like a physical server would. Figure 17-3 shows a diagram representing the relationship between the hypervisor and the guest servers. Virtual Server FIGURE 17-3 Virtual Server Virtual Server Virtual Server Virtual Server Virtual Server Hypervisor Manager Virtual Server Hypervisor Hypervisor Hypervisor Virtual Server Virtual Server Virtual Server Windows Server 2008 R2 Hyper-V Hypervisor Host Server Host Server Host Server Host Server Inside virtual servers the hypervisor normally has a set of tools installed, often called client, or integration, services. These provide a level of integration between the virtual server and its hypervisor that wouldn’t otherwise be possible, such as sharing fi les between hypervisor and client or perhaps synchronizing the system time with the host server. However, also installed is a driver that, on command from the hypervisor, can begin consuming specifi c quantities of memory within the virtual server. We discuss more about these in the “Demand- Based Memory Allocation” section of this chapter but for now it’s suffi cient to say its purpose is to be allocated memory within the virtual server so some of the physical memory the virtual server was previously using can be re-allocated by stealth to another virtual server. It’s called a balloon driver because it infl ates as needed to consume memory within the virtual server’s operating system. Its purpose is not to actually use the memory but to set it aside to ensure that nothing else within the virtual server is using it. In comparison with the virtualization software and technology, there’s very little to say about virtual servers, and that’s a good thing, as the idea of virtualization is to make the fact they’re not running on a physical server invisible to them. While virtual servers can be confi gured to “run” on different physical host servers using technologies like online migration that we’ll cover in the next section, at any point in time, a running virtual
Extended Features of Virtualization ❘ 483 server is assigned to a specifi c physical host server. Virtual servers cannot be allocated and use physical server resources, such as memory, from multiple physical host servers. EXTENDED FEATURES OF VIRTUALIZATION Now that you are familiar with some of the fundamental concepts of virtualization, this section looks at some of the more advanced features and capabilities the technology offers. This is where the unique magic of the technology begins to appear, as some of these concepts simply weren’t available to traditional physical servers for all the time we were using them. While a hypervisor’s primary function is to “run” a virtual server and grant it the resources it requires as it needs them, the current versions of VMware and many of Microsoft’s server virtualization products also provide many of the features discussed in the following sections. Snapshotting Snapshotting a virtual server is very similar to how SQL Server’s own snapshot function works. In principle, the hypervisor suspends the virtual machine, or perhaps requires it to be shut down, and places a point-in-time marker within the virtual machine’s data fi les. From that point on, as changes are made within the virtual machine’s virtual hard drive fi les, the original data is written to a separate physical snapshot fi le by the hypervisor. This can have a slight performance overhead on the I/O performance of the virtual server and, more important, require potentially large amounts of disk space because multiple snapshots can be taken of a virtual server, each having its own snapshot fi le capturing the “before” version of the data blocks. However, a copy of all of the pre-change data gets saved to disk. Having these snapshot fi les available to the hypervisor enables it, upon request, to roll back all the changes in the virtual server’s actual data fi les to the state they were in at the point the snapshot was taken. Once completed, the virtual server will be exactly in the state it was at the point in time the snapshot was taken. While this sounds like a great feature which can offer a level of rollback functionality, it is un-supported by Microsoft for use with virtual servers running SQL Server. Microsoft gives more information about this in the Knowledge Base article 956893; however, until Microsoft supports its use, snapshotting should not be used with virtual servers running SQL Server. High-Availability Features You read earlier that encapsulation means that a virtual server is ultimately just a collection of fi les stored on a fi le system somewhere. These fi les can normally be broken down into the virtual hard drive data fi les, as well as a number of small metadata fi les that give the hypervisor information it needs to “run” the virtual server, such as the CPU, memory, and virtual hard drive confi guration. Keeping these fi les in a centralized storage location — a SAN, for example — enables several different host servers to access the virtual server fi les. The trick that the fi le system and hypervisor have to perform is controlling concurrent read/write access to those fi les in a way that prevents corruption and two host servers running the same virtual server at once.
Page 3:
PROFESSIONAL SQL SERVER® 2012 INTE
Page 7 and 8:
PROFESSIONAL SQL Server ® 2012 Int
Page 9:
For Ava and Leighton, who missed th
Page 12 and 13:
now lives in the South of England,
Page 15 and 16:
ABOUT THE TECHNICAL EDITORS ROBERT
Page 17:
CREDITS EXECUTIVE EDITOR Robert Ell
Page 20 and 21:
I WANT TO ACKNOWLEDGE my wife and c
Page 22 and 23:
CONTENTS xx CHAPTER 3: UNDERSTANDIN
Page 24 and 25:
CONTENTS xxii Lock Modes 167 Compat
Page 26 and 27:
CONTENTS xxiv Tools and Utilities 2
Page 28 and 29:
CONTENTS xxvi Counting the Number o
Page 30 and 31:
CONTENTS xxviii Gathering Sizing Da
Page 32 and 33:
INTRODUCTION WHAT THIS BOOK COVERS
Page 34 and 35:
INTRODUCTION Chapter 2: Demystifyin
Page 36 and 37:
INTRODUCTION Chapter 9: Troubleshoo
Page 38 and 39:
INTRODUCTION xxxvi successful virtu
Page 40 and 41:
INTRODUCTION xxxviii you topics of
Page 43 and 44:
1SQL Server Architecture WHAT’S I
Page 45 and 46:
Isolation The Life Cycle of a Query
Page 47 and 48:
A Basic SELECT Query The Life Cycle
Page 49 and 50:
The Life Cycle of a Query ❘ 9 To
Page 51 and 52:
The Life Cycle of a Query ❘ 11 Be
Page 53 and 54:
The Life Cycle of a Query ❘ 13 it
Page 55 and 56:
The Life Cycle of a Query ❘ 15 6.
Page 57 and 58:
Transaction Log FIGURE 1-6 Buff er
Page 59 and 60:
The Life Cycle of a Query ❘ 19 A
Page 61 and 62:
Recovery Interval The Life Cycle of
Page 63 and 64:
SQL Server’s Execution Model and
Page 65 and 66:
SQL Server’s Execution Model and
Page 67:
Summary ❘ 27 ➤ Checkpoints occu
Page 70 and 71:
30 ❘ CHAPTER 2 DEMYSTIFYING HARDW
Page 72 and 73:
Page 74 and 75:
Page 76 and 77:
Page 78 and 79:
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:
54 ❘ CHAPTER 3 UNDERSTANDING MEMO
Page 96 and 97:
Page 98 and 99:
Page 100 and 101:
Page 102 and 103:
Page 104 and 105:
Page 106 and 107:
Page 108 and 109:
Page 110 and 111:
Page 112 and 113:
Page 114 and 115:
Page 116 and 117:
Page 118 and 119:
78 ❘ CHAPTER 4 STORAGE SYSTEMS By
Page 120 and 121:
80 ❘ CHAPTER 4 STORAGE SYSTEMS To
Page 122 and 123:
82 ❘ CHAPTER 4 STORAGE SYSTEMS Da
Page 124 and 125:
84 ❘ CHAPTER 4 STORAGE SYSTEMS Ch
Page 126 and 127:
86 ❘ CHAPTER 4 STORAGE SYSTEMS Co
Page 128 and 129:
88 ❘ CHAPTER 4 STORAGE SYSTEMS NO
Page 130 and 131:
90 ❘ CHAPTER 4 STORAGE SYSTEMS sn
Page 132 and 133:
92 ❘ CHAPTER 4 STORAGE SYSTEMS Re
Page 134 and 135:
94 ❘ CHAPTER 4 STORAGE SYSTEMS Th
Page 136 and 137:
96 ❘ CHAPTER 4 STORAGE SYSTEMS Mi
Page 138 and 139:
98 ❘ CHAPTER 4 STORAGE SYSTEMS FI
Page 140 and 141:
100 ❘ CHAPTER 4 STORAGE SYSTEMS T
Page 142 and 143:
102 ❘ CHAPTER 4 STORAGE SYSTEMS m
Page 144 and 145:
104 ❘ CHAPTER 4 STORAGE SYSTEMS F
Page 146 and 147:
106 ❘ CHAPTER 4 STORAGE SYSTEMS S
Page 148 and 149:
108 ❘ CHAPTER 4 STORAGE SYSTEMS B
Page 150 and 151:
110 ❘ CHAPTER 4 STORAGE SYSTEMS S
Page 152 and 153:
112 ❘ CHAPTER 5 QUERY PROCESSING
Page 154 and 155:
Page 156 and 157:
Page 158 and 159:
Page 160 and 161:
Page 162 and 163:
Page 164 and 165:
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 189 and 190:
6Locking and Concurrency WHAT’S I
Page 191 and 192:
Database Transactions ❘ 151 succe
Page 193 and 194:
The Dangers of Concurrency ❘ 153
Page 195 and 196:
Now run Session 1; and then as soon
Page 197 and 198:
READ COMMITTED; --REPEATABLE READ;
Page 199 and 200:
FROM Person.Person ORDER BY LastNam
Page 201 and 202:
Double Reads The Dangers of Concurr
Page 203 and 204:
LOCKS Locks ❘ 163 You’ve just r
Page 205 and 206:
COLUMN NAME DESCRIPTION TRANSACTION
Page 207 and 208:
Locks ❘ 167 You may look at this
Page 209 and 210:
WHERE ProductID =1; --ROLLBACK TRAN
Page 211 and 212:
FIGURE 6-13 Locks ❘ 171 The trans
Page 213 and 214:
Compatibility Matrix Locks ❘ 173
Page 215 and 216:
Isolation Levels ❘ 175 Lock escal
Page 217 and 218:
FIGURE 6-18 Repeatable Read Isolati
Page 219:
Summary ❘ 179 the same drawbacks
Page 222 and 223:
182 ❘ CHAPTER 7 LATCHES AND SPINL
Page 224 and 225:
Page 226 and 227:
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 251 and 252:
8Knowing Tempdb WHAT’S IN THIS CH
Page 253 and 254:
Overview and Usage ❘ 213 ➤ Temp
Page 255 and 256:
You can do the same test but with a
Page 257 and 258:
Overview and Usage ❘ 217 Whether
Page 259 and 260:
Overview and Usage ❘ 219 Along th
Page 261 and 262:
Allocation Pages Troubleshooting Co
Page 263 and 264:
SET nocount ON ; DECLARE @i INT = 0
Page 265 and 266:
Troubleshooting Common Issues ❘ 2
Page 267 and 268:
Page 269 and 270:
Page 271 and 272:
Page 273 and 274:
Confi guration Best Practices ❘ 2
Page 275 and 276:
Confi guration Best Practices ❘ 2
Page 277 and 278:
Summary ❘ 237 Once IFI is working
Page 279:
PART II Troubleshooting Tools and L
Page 282 and 283:
242 ❘ CHAPTER 9 TROUBLESHOOTING M
Page 284 and 285:
Page 286 and 287:
Page 288 and 289:
Page 290 and 291:
Page 292 and 293:
Page 294 and 295:
Page 296 and 297:
Page 299 and 300:
10 Viewing Server Performance with
Page 301 and 302:
Performance Monitor Overview ❘ 26
Page 303 and 304:
Show/Hide Counters Performance Moni
Page 305 and 306:
COUNTER DESCRIPTION Database Replic
Page 307 and 308:
COUNTER DESCRIPTION Memory Broker C
Page 309 and 310:
Page 311 and 312:
Working with Data Collector Sets Pe
Page 313 and 314:
Page 315 and 316:
Page 317 and 318:
Using PerfMon on 64-bit Systems Usi
Page 319 and 320:
Types of Bottlenecks Getting More f
Page 321 and 322:
Common Causes of CPU Problems This
Page 323 and 324:
Disk or Storage-Related Problems Ge
Page 325 and 326:
➤ Page latch waits ➤ Waits for
Page 327 and 328:
FIGURE 10-9 Performance Analysis of
Page 329 and 330:
OTHER PERFMON LOG ANALYSIS TOOLS Ot
Page 331 and 332:
Extracting Performance Data for a S
Page 333:
Using LogParser Summary ❘ 293 Log
Page 336 and 337:
296 ❘ CHAPTER 11 CONSOLIDATING DA
Page 338 and 339:
Page 340 and 341:
Page 342 and 343:
Page 344 and 345:
Page 346 and 347:
Page 348 and 349:
Page 350 and 351:
Page 352 and 353:
Page 354 and 355:
Page 356 and 357:
Page 358 and 359:
Page 360 and 361:
Page 362 and 363:
Page 365 and 366:
12 Bringing It All Together with SQ
Page 367 and 368:
Getting Familiar with SQL Nexus ❘
Page 369 and 370:
Page 371 and 372:
Page 373 and 374:
Page 375 and 376:
FIGURE 12-11 Getting Familiar with
Page 377 and 378:
Page 379 and 380:
Page 381 and 382:
➤ Importing SQL Trace fi les usin
Page 383 and 384:
page. Figure 12-19 shows the Manage
Page 385 and 386:
Customizing SQL Nexus ❘ 345 NOTE
Page 387 and 388:
Resolving Common Issues ❘ 347 pre
Page 389 and 390:
13 Diagnosing SQL Server 2012 Using
Page 391 and 392:
WHY YOU SHOULD BE USING EXTENDED EV
Page 393 and 394:
What Are Extended Events? ❘ 353 e
Page 395 and 396:
What Are Extended Events? ❘ 355 S
Page 397 and 398:
What Are Extended Events? ❘ 357 Y
Page 399 and 400:
Targets What Are Extended Events?
Page 401 and 402:
What Are Extended Events? ❘ 361 T
Page 403 and 404:
Creating Extended Events Sessions i
Page 405 and 406:
Once events have been added, as sho
Page 407 and 408:
FIGURE 13-12 Once the session has b
Page 409 and 410:
insert t1 (val1, val2) values ('X',
Page 411 and 412:
Viewing Data Captured by Extended E
Page 413 and 414:
This will reconfi gure the live dat
Page 415 and 416:
FIGURE 13-27 FIGURE 13-28 Viewing D
Page 417:
Summary ❘ 377 For newcomers to th
Page 420 and 421:
380 ❘ CHAPTER 14 ENHANCING YOUR T
Page 422 and 423:
Page 424 and 425:
Page 426 and 427:
Page 428 and 429:
Page 430 and 431:
Page 432 and 433:
Page 434 and 435:
Page 436 and 437:
Page 438 and 439:
Page 440 and 441:
Page 442 and 443:
Page 444 and 445:
Page 446 and 447:
406 ❘ CHAPTER 15 DELIVERING A SQL
Page 448 and 449:
Page 450 and 451:
Page 452 and 453:
Page 454 and 455:
Page 456 and 457:
Page 458 and 459:
Page 460 and 461:
Page 462 and 463:
Page 464 and 465:
Page 466 and 467:
Page 468 and 469:
Page 470 and 471:
Page 472 and 473: 432 ❘ CHAPTER 15 DELIVERING A SQL
Page 485 and 486: 16 Delivering Manageability and Per
Page 487 and 488: POLICY-BASED MANAGEMENT Policy-Base
Page 489 and 490: FIGURE 16-1 6. Right-click on Polic
Page 491 and 492: 3. Type the name of the instance th
Page 493 and 494: Policy-Based Management ❘ 453 aut
Page 495 and 496: TABLE 16-5: Example File Autogrow P
Page 497 and 498: FIGURE 16-7 Policy-Based Management
Page 499 and 500: Policy-Based Management ❘ 459 Onc
Page 501 and 502: Other Microsoft Tools for Managing
Page 507: You also worked through detailed ex
Page 510 and 511: 470 ❘ CHAPTER 17 RUNNING SQL SERV
Page 549 and 550: INDEX Numbers 32-bit operating syst
Page 551 and 552: loat, 67, 74 block-based storage sy
Page 553 and 554: Memory Broker Clerks, 267 Memory No
Page 555 and 556: of SCOM, 464-465 of virtual databas
Page 557 and 558: Fibre Channel Internet Protocol (FC
Page 559 and 560: I IA-64, 57 IAM (Index Allocation M
Page 561 and 562: monitoring, 163-165 NOLOCK hint for
Page 563 and 564: multi-layer (MLC) fl ash memory, 10
Page 565 and 566: performance baselines for, 285 bott
Page 567 and 568: data analysis in, 255 feature-speci
Page 569 and 570: Reliability and Performance Monitor
Page 571 and 572: SGAM (Shared Global Allocation Map)
Page 573 and 574:
in tempdb, 214-215 wait, 284-285 st
Page 575 and 576:
triggers, 217-218 trivial plans, 10
Page 577 and 578:
VLF (Virtual Log File) count, 428-4
Page 580:
Related Wrox Books Professional Mic
show all

SQL SERVER 2008

Create successful ePaper yourself

Delete template?

Save as template?