Tuesday, May 29, 2012

SQL 2012 Upgrade Gotcha: "Windows PowerShell 2.0 already installed" rule failure

SQL Server 2012 requires PowerShell 2.0 to be installed on the machine you're putting SQL 2012 on. So, if you're running an instance of SQL Server prior to 2012 that you want to upgrade on a Windows Server 2008 R1 machine, you will need to install PowerShell 2.0 first.

Friday, May 25, 2012

SQL 2012 Upgrade Gotcha: Network Backup Location

If you have your database backup location set to a network (UNC) path you might run into the following error during an upgrade of the Data Engine to SQL Server 2012. I think the upgrade process runs under the Local System account so it doesn't have permission to modify rights on the network location.

Updating permission setting for folder '\\<network path>' failed. The folder permission setting were supposed to be set to '<some gobbledy-gook that looks permissions and a SID>'.

Thursday, May 17, 2012

Saving changes is not permitted?!

So, you are working on a database where you have DDL permissions, if not db_owner, but SQL Server Management Studio barks at you because you want to insert a new column in the middle of the table. The message you get looks something like this [emphasis added]:
Saving changes is not permitted. The changes you have made require the following tables ot be dropped and re-created. You have either made changes to a table that can't be re-created or enabled the option Prevent saving changes that require the table to be re-created.
<List of tables>

Wednesday, May 9, 2012

Installing SQL Server 2012 Upgrade Advisor

We're hot and heavy into upgrading our BI environment from SQL Server 2008 R2 to 2012 and plan to go live around the middle of next month. To that end, I am in the process of running the SQL Server 2012 Upgrade Advisor on copies of our production servers. Before we can run it, however, we have to get it installed. That turned out to be a little on the obtuse side.

Greetings Business Intelligence people!

I am a DBA-turned-BI Administrator. I'm not sure I like the term BI Administrator but it's a role that's a whole lot different than the traditional DBA. In fact, where I work, I don't even have to worry about some of the traditional DBA stuff. I am lucky enough to have a great team of folks that make sure my SQL Servers stay up and that all those databases get backed up properly. So, I get to focus on making sure that the performance of our BI systems is up-to-snuff. We use the Microsoft Business Intelligence stack from SQL Server to SharePoint. (Our SSRS implementation is managed by our fine SharePoint team, more luck for me!)

Given all that, this blog is about the administration of Microsoft SQL Server and all it's related products with a focus on BI performance and manageability. Sometimes the content will be relevant for Developers - note the capital D, I was a Developer once and I am proud of it - since a lot of the performance work in the BI space falls to them; however, my hope is that the content here will help administrators get the most of out of their Microsoft BI solutions and help them work closely with the BI Developers to build them right from the start.