Sql server enterprise edition awareness
•Download as PPTX, PDF•
0 likes•463 views
Why do we need to purchase SQL Server Enterprise Edition? SQL Server Enterprise Edition has few great internal features that can help any organization to run safest and fastest database environment.
Recommended
Recommended
More Related Content
What's hot
What's hot (17)
Viewers also liked
Viewers also liked (14)
Similar to Sql server enterprise edition awareness
Similar to Sql server enterprise edition awareness (20)
More from Hamid J. Fard
More from Hamid J. Fard (12)
Recently uploaded
Recently uploaded (20)
Sql server enterprise edition awareness
- 1. SQL SERVER ENTERPRISE AWARENESS By Hamid J. Fard Microsoft Certified Master: SQL Server 2008 Microsoft Certified Solutions Master: Charter-Data Platform CIW Database Design Specialist Copyrights © 2016 Fard Solutions Sdn Bhd, All rights reserved.
- 2. Agenda • What MattersToYou? • DoYou Believe in High End Hardware? • SQL Server Enterprise Edition (Internal Features) • Advance Scan (Merry-Go-Round) • Fast Recovery • Prefetching • Single Scatter Scan • Automation Matching • Role Reversal • Partitioning • Data Compression • DeferredTransaction • Resource Governor • Vardecimal Storage Formatting • Conclusion Copyrights © 2016 Fard Solutions Sdn Bhd, All rights reserved.
- 3. What MattersToYou? Manageability Performance Storage Space Disaster Recovery Cost Copyrights © 2016 Fard Solutions Sdn Bhd, All rights reserved.
- 4. DoYou Believe in High End Hardware? YES NO Without High End Software,Your High End Hardware IsWorthless. Copyrights © 2016 Fard Solutions Sdn Bhd, All rights reserved.
- 5. SQL Server Internal Features vs. Editions Feature Enterprise Standard Advance Scan (Merry-Go-Round) Fast Recovery Prefetching Single Scatter Scan Automation Matching Role Reversal Partitioning Data Compression DeferredTransaction Resource Governor Vardecimal Storage Formatting Copyrights © 2016 Fard Solutions Sdn Bhd, All rights reserved.
- 6. Advance Scan (Marry-Go-Round) Copyrights © 2016 Fard Solutions Sdn Bhd, All rights reserved. Table A User A User B SQL Server Optimizer Engine Query Buffer Query Buffer Query BufferRead
- 7. Fast Recovery Analysis Phase Redo Phase Undo Phase Database Recovery Lifecycle Database is Available By Lock-Logging Database is Under Recovery UncommittedTransactions are Roll-Backed Copyrights © 2016 Fard Solutions Sdn Bhd, All rights reserved.
- 8. Prefetching Select E.ID, E.FN, E.LN, D.Designation From Employee E Inner Join Designation D On E.Designation_ID = D.ID Designation Employee Read Synchronously Read Asynchronously Project Resultset Copyrights © 2016 Fard Solutions Sdn Bhd, All rights reserved.
- 9. Single Scatter Scan Copyrights © 2016 Fard Solutions Sdn Bhd, All rights reserved. 465 308 488 489 ListofLeafPages
- 10. Automation Matching CreateTable dbo.Test (ID Bigint, Batch Char(10), BatchID As Cast(ID As Char) + Batch Persisted) Select ID, Batch From dbo.Test Where Cast ( ID As Char ) + Batch = ‘1045623’ Select ID, Batch From dbo.Test Where BatchID = ‘1045623’ ConvertsTo Copyrights © 2016 Fard Solutions Sdn Bhd, All rights reserved.
- 11. Role Reversal Copyrights © 2016 Fard Solutions Sdn Bhd, All rights reserved. Build Input Probe Input Hash MatchResultset
- 12. Partitioning Copyrights © 2016 Fard Solutions Sdn Bhd, All rights reserved. Dbo.Sales 2016-2017 Filegroup 1 Dbo.Sales 2015-2016 Filegroup 2 Dbo.Sales 2014-2015 Filegroup 3 Query Dbo.Sales
- 13. Data Compression Copyrights © 2016 Fard Solutions Sdn Bhd, All rights reserved. dbo.Sales 1 Billion Rows 186GB Data Size 23,250,000,000,000 Data Pages dbo.Sales 1 Billion Rows 108GB Data Size 1,4557,760,000 Data Pages Data Compression Up to 40%
- 14. DeferredTransaction Copyrights © 2016 Fard Solutions Sdn Bhd, All rights reserved. In Other Editions, A CorruptedTransaction Causes Database StartupTo Fail Analysis Phase Roll Forward Phase Roll Back Phase Transaction Recovery Lifecycle Transaction Uncommitted Transaction Not Rolled Back Due toCorruptedTransaction Log I/O
- 15. Resource Governor Copyrights © 2016 Fard Solutions Sdn Bhd, All rights reserved. Memory: 64GB Processor: 8 Logical Processor DB_A Max Memory: 12GB Max Processor: 2 Logical Processors Max IOPS: 500 DB_B Max Memory: 24GB Max Processor: 4 Logical Processors Max IOPS: 2000 AppA App B
- 16. Vardecimal Storage Formatting Copyrights © 2016 Fard Solutions Sdn Bhd, All rights reserved. ID Full Name Savings 1 John Smith 50,000 2 BillGates 97,000,000,000 3 KevinWood 500 20 Bytes 20 Bytes 20 Bytes ID Full Name Savings 1 John Smith 50,000 2 BillGates 97,000,000,000 3 KevinWood 500 5 Bytes 20 Bytes 5 Bytes
- 17. Conclusion If SQL Server Enterprise is Expensive, What About Other Editions! Copyrights © 2016 Fard Solutions Sdn Bhd, All rights reserved.
Editor's Notes
- Ask participants what matters to them? Are they willing to have all? Explain as following:- Manageability: That’s great if the DBA can manage every single database within the SQL Server farm from one workstation or apply some policy to avoid some development mistakes. SQL Server enterprise edition provides some features for better and easier manageability of databases such as policy base management, resource governor, management data warehouse, master and slave agents and so on. Performance: Enterprise edition provides high performance due to having some unique internal features which is discussed in the next slides. Storage Space: By using Enterprise edition, you do not need to have huge amount of storage space, you can reduce the storage size by 50%. Disaster Recovery: We are not going to talk about HADR, we are here to talk about database corruption recovery that other editions are not able to support it. Cost: Emm… To gain mentioned benefits, for sure you need to spend some money! Nothing comes free.
- Explain audience that why they should not believe in high end hardware. Mention that high end hardware does not change SQL Server behavior towards data and transaction management. So if even the hardware is with high specs, it does not make any changes on the SQL Server behavior. For example: Corrupted I/O can happened in the high back end hardware and it can cause SQL Server database to be suspended.
- 1- Advance Scan (Merry Go Round Algorithm): This feature allows multiple tasks to share full table scans. If the execution plan of a Transact-SQL statement requires a scan of the data pages in a table and the Database Engine detects that the table is already being scanned for another execution plan, the Database Engine joins the second scan to the first, at the current location of the second scan. The Database Engine reads each page one time and passes the rows from each page to both execution plans. This continues until the end of the table is reached. Without advanced scanning, each user would have to compete for buffer space and cause disk arm contention. The same pages would then be read once for each user, instead of read one time and shared by multiple users, slowing down performance and taxing resources. 2- Fast Recovery: Fast Recovery allows a database to come online as soon as the REDO phase completes, before UNDO is run. This is made possible by lock logging, which records the locks that were applied by a transaction in the associated log record. 3- Prefetching: The leaf rows of a non-clustered index contain pointers to the data rows that contain each specific key value. As the storage engine reads through the leaf pages of the non-clustered index, it also starts scheduling asynchronous reads for the data rows whose pointers have already been retrieved. 4- Single Scatter Scan: The SQL Server storage engine scans the intermediate index page and builds a list of the leaf pages that must be read. The storage engine then schedules all the reads in key order. It also recognizes that for instance pages 308/465 and 488/489 are contiguous and performs a single scatter read to retrieve the adjacent pages in a single operation. 5- Automatic Matching: The Query Optimizer automatically matches the computed column definition to an existing scalar expression in a query. 6- Role Reversal: In Hash Join, after the build input is hashed, the second table, called the probe input, will be read and compared to the hash table. If rows are matched they will be returned. On the execution plan, the table at the top will be used as the build input, and the table at the bottom as the probe input. If the Query Optimizer is not able to correctly estimate which of the two inputs is smaller, the build and probe roles may be reversed at execution time, and this will not be shown on the execution plan. 7- Partitioning: You can transfer or access subsets of data quickly and efficiently, while maintaining the integrity of a data collection. For example, an operation such as loading data from an OLTP to an OLAP system takes only seconds, instead of the minutes and hours the operation takes when the data is not partitioned. And it improve query performance, based on the types of queries you frequently run and on your hardware configuration. For example, the query optimizer can process equi-join queries between two or more partitioned tables faster when the partitioning columns in the tables are the same, because the partitions themselves can be joined. 8- Data Compression: This feature is to reduce the size of the database. In addition to saving space, data compression can help improve performance of I/O intensive workloads because the data is stored in fewer pages and queries need to read fewer pages from disk. 9- Deferred Transaction: A deferred transaction is a transaction that is uncommitted when the roll forward phase finishes and that has encountered an error that prevents it from being rolled back. Because the transaction cannot be rolled back, it is deferred. In other editions, a corrupted transaction causes database startup to fail. 10- Vardecimal Storage Formatting: This storage format can be enabled at a table-level granularity. When enabled, SQL Server stores decimal and numeric data in the variable portion of the row instead the fixed portion. You can use vardecimal storage format to reduce the size of your database if you have tables with decimal and numeric data types.
- 1- Advance Scan (Merry Go Round Algorithm): This feature allows multiple tasks to share full table scans. If the execution plan of a Transact-SQL statement requires a scan of the data pages in a table and the Database Engine detects that the table is already being scanned for another execution plan, the Database Engine joins the second scan to the first, at the current location of the second scan. The Database Engine reads each page one time and passes the rows from each page to both execution plans. This continues until the end of the table is reached. Without advanced scanning, each user would have to compete for buffer space and cause disk arm contention. The same pages would then be read once for each user, instead of read one time and shared by multiple users, slowing down performance and taxing resources.
- 2- Fast Recovery: Fast Recovery allows a database to come online as soon as the REDO phase completes, before UNDO is run. This is made possible by lock logging, which records the locks that were applied by a transaction in the associated log record.
- 3- Prefetching: The leaf rows of a non-clustered index contain pointers to the data rows that contain each specific key value. As the storage engine reads through the leaf pages of the non-clustered index, it also starts scheduling asynchronous reads for the data rows whose pointers have already been retrieved.
- 4- Single Scatter Scan: The SQL Server storage engine scans the intermediate index page and builds a list of the leaf pages that must be read. The storage engine then schedules all the reads in key order. It also recognizes that for instance pages 308/465 and 488/489 are contiguous and performs a single scatter read to retrieve the adjacent pages in a single operation.
- 5- Automatic Matching: The Query Optimizer automatically matches the computed column definition to an existing scalar expression in a query.
- 6- Role Reversal: In Hash Join, after the build input is hashed, the second table, called the probe input, will be read and compared to the hash table. If rows are matched they will be returned. On the execution plan, the table at the top will be used as the build input, and the table at the bottom as the probe input. If the Query Optimizer is not able to correctly estimate which of the two inputs is smaller, the build and probe roles may be reversed at execution time, and this will not be shown on the execution plan.
- 7- Partitioning: You can transfer or access subsets of data quickly and efficiently, while maintaining the integrity of a data collection. For example, an operation such as loading data from an OLTP to an OLAP system takes only seconds, instead of the minutes and hours the operation takes when the data is not partitioned. And it improve query performance, based on the types of queries you frequently run and on your hardware configuration. For example, the query optimizer can process equi-join queries between two or more partitioned tables faster when the partitioning columns in the tables are the same, because the partitions themselves can be joined.
- 8- Data Compression: This feature is to reduce the size of the database. In addition to saving space, data compression can help improve performance of I/O intensive workloads because the data is stored in fewer pages and queries need to read fewer pages from disk.
- 9- Deferred Transaction: A deferred transaction is a transaction that is uncommitted when the roll forward phase finishes and that has encountered an error that prevents it from being rolled back. Because the transaction cannot be rolled back, it is deferred. In other editions, a corrupted transaction causes database startup to fail.
- 10- Vardecimal Storage Formatting: This storage format can be enabled at a table-level granularity. When enabled, SQL Server stores decimal and numeric data in the variable portion of the row instead the fixed portion. You can use vardecimal storage format to reduce the size of your database if you have tables with decimal and numeric data types.