|
|
|
|
| LEADER |
06111nmm a2200541 u 4500 |
| 001 |
EB001946137 |
| 003 |
EBX01000000000000001109039 |
| 005 |
00000000000000.0 |
| 007 |
cr||||||||||||||||||||| |
| 008 |
210123 ||| eng |
| 020 |
|
|
|a 9781430267423
|
| 050 |
|
4 |
|a QA76.9.D3
|
| 100 |
1 |
|
|a Fritchey, Grant
|
| 245 |
0 |
0 |
|a SQL Server query performance tuning
|c Grant Fritchey
|
| 250 |
|
|
|a Fourth edition
|
| 260 |
|
|
|a Berkeley, CA, New York, NY
|b Apress, Distributed to the Book trade worldwide by Springer
|c 2014
|
| 300 |
|
|
|a xxix, 612 pages
|b illustrations
|
| 505 |
0 |
|
|a Chapter 3: Disk Performance AnalysisDisk Bottleneck Analysis; Disk Counters; % Disk Time; Current Disk Queue Length; Disk Transfers/Sec; Disk Bytes/Sec; Avg. Disk Sec/Read and Avg. Disk Sec/Write; Additional I/O Monitoring Tools; Sys.dm_io_virtual_file_stats; Sys.dm_os_wait_stats; Disk Bottleneck Resolutions; Optimizing Application Workload; Using a Faster I/O Path; Using a RAID Array; RAID 0; RAID 1; RAID 5; RAID 6; RAID 1+0 (RAID 10); Using a SAN System; Using Solid State Drives; Aligning Disks Properly; Adding System Memory; Creating Multiple Files and Filegroups
|
| 505 |
0 |
|
|a Moving the Log Files to a Separate Physical DiskUsing Partitioned Tables; Summary; Chapter 4: CPU Performance Analysis; Processor Bottleneck Analysis; % Processor Time; % Privileged Time; Processor Queue Length; Context Switches/Sec; Batch Requests/Sec; SQL Compilations/Sec; SQL Recompilations/Sec; Other Tools for Measuring CPU Performance; Sys.dm_os_wait_stats; Sys.dm_os_workers and Sys.dm_os_schedulers; Processor Bottleneck Resolutions; Optimizing Application Workload; Eliminating Excessive Compiles/Recompiles; Using More or Faster Processors; Not Running Unnecessary Software
|
| 505 |
0 |
|
|a Target Server Memory (KB) and Total Server Memory (KB)Additional Memory Monitoring Tools; DBCC MEMORYSTATUS; Dynamic Management Objects; Sys.dm_os_memory_brokers; Sys.dm_os_memory_clerks; Sys.dm_os_ring_buffers; Sys.dm_db_xtp_table_memory_stats; Sys.dm_xtp_system_memory_consumers; Memory Bottleneck Resolutions; Optimizing Application Workload; Allocating More Memory to SQL Server; Moving In-Memory Tables Back to Standard Storage; Increasing System Memory; Changing from a 32-Bit to a 64-Bit Processor; Compressing Data; Enabling 3GB of Process Address Space; Addressing Fragmentation; Summary
|
| 505 |
0 |
|
|a Improper Use of CursorsImproper Configuration of the Database Transaction Log; Excessive Use or Improper Configuration of tempdb; Summary; Chapter 2: Memory Performance Analysis; Performance Monitor Tool; Dynamic Management Objects; Hardware Resource Bottlenecks; Identifying Bottlenecks; Bottleneck Resolution; Memory Bottleneck Analysis; SQL Server Memory Management; Available Bytes; Pages/Sec and Page Faults/Sec; Paging File %Usage and Page File %Usage; Buffer Cache Hit Ratio; Page Life Expectancy; Checkpoint Pages/Sec; Lazy Writes/Sec; Memory Grants Pending
|
| 505 |
0 |
|
|a At a Glance; Introduction; Chapter 1: SQL Query Performance Tuning; The Performance Tuning Process; The Core Process; Iterating the Process; Performance vs. Price; Performance Targets; "Good Enough" Tuning; Performance Baseline; Where to Focus Efforts; SQL Server Performance Killers; Insufficient Indexing; Inaccurate Statistics; Improper Query Design; Poorly Generated Execution Plans; Excessive Blocking and Deadlocks; Non-Set-Based Operations; Inappropriate Database Design; Excessive Fragmentation; Nonreusable Execution Plans; Frequent Recompilation of Queries
|
| 653 |
|
|
|a Bases de données / Interrogation
|
| 653 |
|
|
|a Querying (Computer science) / fast
|
| 653 |
|
|
|a Bases de données / Gestion
|
| 653 |
|
|
|a SQL server / fast
|
| 653 |
|
|
|a Querying (Computer science) / http://id.loc.gov/authorities/subjects/sh2005008252
|
| 653 |
|
|
|a online searching / aat
|
| 653 |
|
|
|a Database searching / fast
|
| 653 |
|
|
|a SQL server / http://id.loc.gov/authorities/names/n90684343
|
| 653 |
|
|
|a Database management / http://id.loc.gov/authorities/subjects/sh85035848
|
| 653 |
|
|
|a Database searching / http://id.loc.gov/authorities/subjects/sh86007858
|
| 653 |
|
|
|a SQL server / blmlsh
|
| 653 |
|
|
|a COMPUTERS / Programming Languages / SQL. / bisacsh
|
| 653 |
|
|
|a Database management / fast
|
| 041 |
0 |
7 |
|a eng
|2 ISO 639-2
|
| 989 |
|
|
|b OREILLY
|a O'Reilly
|
| 490 |
0 |
|
|a The expert's voice in SQl server
|
| 024 |
8 |
|
|a 10.1007/978-1-4302-6742-3
|
| 776 |
|
|
|z 9781430267430
|
| 776 |
|
|
|z 1430267429
|
| 776 |
|
|
|z 9781430267423
|
| 776 |
|
|
|z 1430267437
|
| 856 |
4 |
0 |
|u https://learning.oreilly.com/library/view/~/9781430267423/?ar
|x Verlag
|3 Volltext
|
| 082 |
0 |
|
|a 658
|
| 082 |
0 |
|
|a 500
|
| 082 |
0 |
|
|a 005.74068
|
| 520 |
|
|
|a Queries not running fast enough? Wondering about the in-memory database features in 2014? Tired of phone calls from frustrated users? Grant Fritchey?s book SQL Server Query Performance Tuning is the answer to your SQL Server query performance problems. The book is revised to cover the very latest in performance optimization features and techniques, especially including the newly-added, in-memory database features formerly known under the code name Project Hekaton. This book provides the tools you need to approach your queries with performance in mind. SQL Server Query Performance Tuning leads you through understanding the causes of poor performance, how to identify them, and how to fix them. You?ll learn to be proactive in establishing performance baselines using tools like Performance Monitor and Extended Events. You?ll learn to recognize bottlenecks and defuse them before the phone rings. You?ll learn some quick solutions too, but emphasis is on designing for performance and getting it right, and upon heading off trouble before it occurs. Delight your users. Silence that ringing phone. Put the principles and lessons from SQL Server Query Performance Tuning into practice today. Covers the in-memory features from Project Hekaton Helps establish performance baselines and monitor against them Guides in troubleshooting and eliminating of bottlenecks that frustrate users
|