![SQL-Server-2012[1]](http://blog.appliedis.com/wp-content/uploads/2013/05/SQL-Server-20121.jpg)
Turns out we had installed SQL 2012 but not SQL 2012 SP1. Power View gets a number of important upgrades in SP1, including much-needed filtering that’s missing from the earlier version, as well as my eagerly anticipated Map chart type. Read More…
Turns out we had installed SQL 2012 but not SQL 2012 SP1. Power View gets a number of important upgrades in SP1, including much-needed filtering that’s missing from the earlier version, as well as my eagerly anticipated Map chart type. Read More…
During this session I found it interesting how much time was spent talking about mirroring. Mirroring is now considered a deprecated technology but is still supported by SharePoint 2013. Today I’d like to break down the session and talk about my thoughts on each point.
We’ve already discussed AlwaysOn High Availability, and integrated SSRS. Today I want to talk about the new contained database feature of SQL Server 2012. Contained databases make the life of the DBA and developer much easier. They also streamline the deployment of high availability scenarios.
So what are some of the new offerings of this feature?
Now that we’ve already discussed AlwaysOn High Availability, today I want to talk about the changes made to Integrated SQL Reporting Services. Integrated SSRS is used to generate reports in a SharePoint environment. Historically it has been very tricky to configure and maintain.
So what are some of the improvements that now make it easier? Read More…
First up, I want to talk about AlwaysOn High Availability (HA). In short, this feature combines the best of clustering and mirroring to make your applications highly available.
So why is this new feature so cool?
Every staging project has two elements: the ETL itself and a staging data structure. So today I’d like to talk about best practices for standing up a staging area using SQL Server Integration Services [ETL] and hosting a staging database in SQL Server 2012 [DB]. The ‘best practices’ are across three areas: Architecture, Development, and Implementation & Maintenance of the solution. Each area represents key patterns and practices (not a comprehensive list) for the ETL component and the data structure of the staging database.
And since I presume readers are looking for best practices silver bullets, that is what I will try to deliver. What you will not find in this post are turnkey ETL performance optimizations.