More information here.
With that note, we conclude this event tonight. Good night everyone. Thanks for tuning in.
Prithvi will take questions now. He is done with his presentation.
Physical IO extension to Resource Governor. Azure integration and backup encryption are some other features. – Prithvi
Generally, long operations get locked due to activities. You can’t skip to the next task instead. – Prithvi
Incremental updates reduces windows. They are dropped and created. – Prithvi
Buffer pool= memory for Data. This feature allows data pages temporary park in SSD. – Prithvi
One great limitation in Columnstore indexes is removed making it a presentable edition. – Prithvi
Currently, some of the features are limited since it just got released recently. – Prithvi
No clustered index, foreign keys and triggers are allowed either. – Prithvi
We have a few new Data Types in SQL Server 2014. CLRs are discontinued. – Prithvi
2 values can crate the same # value. Create # values so that your search is narrowed. – Pritvi
Benefits of MOT : No fragmentation and no locks/latches. – Prithvi
Prithvi now talks about Memory-optimized tables. This definitely impacts on performance.
Even Dinesh Priyannkara did a session about the same topic few meetups ago. So Prithvi will be quick.
Prithvi will not be talking about every new feature of SQL Server 2014, since it will take much more time for him.
Prithvi will discusses new features in SQL Server 2014, and review them.
Second speaker for days would be Prithiviraj Kulasingham, MVP, Principal Database Administrator (Pearson Lanka).
Video by them.
Today we have a special event partner. GUNNAR EYE WEARS. They will demo their product and video.
We are back.
Before we move on to the second speaker, we will be having a small refreshments break.
Bathige will now asks questions and will give away goodies.
Susantha concludes his session and no questions are asked from him.
How to remove execution plans? Clear the cache and buffer pool. – Bathige
Query stats: gives you aggregated info about the queries executed against the DB. – Bathige
Query # are used to identify similar queries. – Bathige
You can pass the SQL handle in to hexadecimal. – Bathige
Tip: You can consider creating one parameterized statement or consider using plan guides. – Bathige
If single-use plans are >50%, it is recommended to enable ‘optimeze for ad-hoc workload’ option. – Bathige
Even though Plan handle can be different, functionally plans could be similar. – Bathige
Bathige now is going to Clear the cache of a DB/table with a query. Which he says is dangerous method.
You can filter out operations by filtering with index scan. – Bathige
Similarly you can check for implicit check warnings. Which could be having key lookups. – Bathige
Plan data is stored internally as XML. If you can manipulate these structured xml values, you can retrieve many data. – Bathige
Bathige now talks about Useful queries which can help you to find single use-plans. He will be demo-ing later on.
The Plan Cache is an important aspect of SQL Server memory which stores execution plans for various SQL Server objects. This session will introduce you to the Plan Cache, and provide you tips on maximizing re-use of cached plans, troubleshooting plan cache related issues, eliminating unnecessary recompilation and minimizing plan cache pollution.
First of all we have Susantha Bathige, who is from Pearson Lanka and will be talking on What you should know about the SQL Server Plan Cache
This is Team Digit Live from Microsoft SL Office for SQL May Meetup.