You've migrated parts of your application to in-memory. But now you are not seeing a serious performance improvement, or maybe even a performance degradation! What's going on? In this session we walk you through several performance problems we have seen with customers, and show how to diagnose and resolve the issues to ultimately obtain the performance improvement you're looking for from in-memory OLTP. We address a variety of issues, including log IO bottlenecks, index tuning, and query plan problems.
Over the last years, many customers have had to deal with cyber attacks targeted at intellectual property. We have entered a new phase in which criminals unleash destructive attacks, rendering IT environments unusable and effectively halting business. Consumerization of IT and the cloud add inherent tension and security implications to this new reality. How can one deal with data that moves in and out of your datacenters, to unmanaged devices and cloud services not directly under your control? How can you create a cost efficient architecture and plan for prevention, detection, and recovery in a time where cloud and consumerization of IT are high on every CxO's agenda? The presenters of this session have been on the Targeted Attack frontline with enterprise customers over the last years. They explain the threats of targeted attacks and share an architecture model using a data classification model, as well as their field experiences and services you can leverage to deal with prevention, detection and recovery.
SharePoint 2013 is not just a collection of lists and libraries anymore. It is a big product with lots of built-in out of the box services. We as SharePoint developers used to build a lot on the top of SharePoint, but with rapidly growing product functionality, there is less need for developing custom code. In fact there is more need for consultants that they know SharePoint out of the box services and features and they also know how to configure and use them. The new generation of SharePoint architects, have deep understanding of built-in services and their limits so that they can decide whether to develop custom code or just enable a built-in Service. This approach makes SharePoint development quick and dramatically reduces the cost of maintenance and support.