Join the Windows Server and Microsoft System Center product teams once again as we take a deeper dive into the automation specifics related to tenant provisioning in the Azure Pack solution. In this session we explore the functionality and examine each Service Management Automation (SMA) Runbook. If you haven't seen SMA in action yet, this is a must-see session and a great way to get started. Session includes links to free downloadable content of the demo and example solution (from post found at http://aka.ms/IntroToSMA).
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.
ASP.NET vNext is a lean and composable framework for building web and cloud applications. ASP.NET vNext is fully open source and available on GitHub. ASP.NET vNext is currently in preview, and in this talk Fowler and Edwards will put it all into Context. vNext apps can use a cloud-optimized subset of the .NET framework. This subset of the framework is about 11 megabytes in size compared to 200 megabytes for the full framework, and is composed of a collection of NuGet packages. What does that mean for compatibility? When would you choose vNext and when would you not? You don't have to use Visual Studio to develop ASP.NET vNext applications. You can develop and run vNext on platforms that Visual Studio doesn't run on. But Visual Studio provides the best development experience, and we'll cover ASP.NET vNext both inside and outside the IDE.