Ok, I know Microsoft isn't big on following laid out standards, but it doesn't stop it from causing headaches. Today I found out that a simple column rename in SQL server is not possible with standard, well documented SQL. alter table tablename change oldname newname varchar (10); Instead I have to use some sort of SQL Server procedure sp_rename sp_rename 'TableName.ColumnName', 'NewColumnName', 'COLUMN'

Here's a tip for copying a database in SQL Server 2008 (maybe other versions) via the Copy Database wizard.

When I initially tried the wizard it failed with Message: Access to the path 'E:DataMicrosoft SQL ServerMSSQL10_50.MSSQLSERVERMSSQLDATANEWDATABASENAME.mdf' is denied.

In this case the NETWORK SERVICE was not able to create the new MDF file. I had to do add this user with FULL CONTROL to the MSSQLDATA directory and the wizard ran with no complications.

  1. Navigate to data folder
  2. Right click -> Properties
  3. Click the Security tab
  4. Click the Edit button to change permissions
  5. Click the Add button to add a new group or user
  6. Search for "NETWORK SERVICE" and click Add
  7. Click the Full Control checkbox for the newly added user

In case you're trying to find the wizard, right click the database, pick tasks, then Copy Database.

Microsoft Hat
27 October 2008

Those of you who know me may know that I am slightly opposed to Microsoft products. This stems mostly from my anti-institutionalism and fondness for the open source community. Really, it all started with price. So you could say that my Mennonite heritage is what has produced my technological stance.

With that said, for the next several weeks, probably months, I will be donning a Microsoft hat for a project I have been assigned at work. I will be setting up a Sharepoint Intranet for one of our clients. This is as Microsoft as you can get. I will be working with all things Microsoft: MS Office, MS Projects, Active Directory etc.

I am approaching this with an open mind. I am actually interested in seeing how this turns out and learning a bit more about the world of Microsoft. It's definitely something that would look good on the resume. As I have said to a few people: "If it comes to the worst, at least I'll have a reason to not like Microsoft."