I wish that I had great things to say regarding running a migration using SQL Server 2008 but I don’t.
Strike One: I couldn’t run a simple EPiServer CMS5 installation to the sql server. I kept getting this error:
Error – User ’dbo’ does not have permission to run DBCC TRACEON
After some searching I came to the conclussion that the only thing one could do to override this is to give my user sysadmin rights. Something that not many customers fancy giving away. But it did actually work and the insallation was successful.
Strike Two: With a fresh epi5 site installed and my original site upgraded to 4.62b and ready to rock, I started to run the migration tool. The Result? ”Migrating Data…” And nothing else. It didn’t really start the job and just died there. I even gaved it 12 hours (over the night) and nothing happened. I still had sysadmin rights so that wasn’t it.
Strike Three: With not much patience left I tried to do a workaround, i.e to backup the Databases and restored them on a 2005 machine, then do the migration and then back to the 2008 machine. The problem is that SQL Server doesn’t have backward compatibility 🙁
So basicly I’m going to reproduce everything on the 2005 machine and work from that one. Once done, I’ll do a backup and then restore that to the sql server 2008 and have the final product running on that one. Not the best solution.
I’ve a case open @ EPiServer and who knows, maybe they have a solution for this. I’ll be sure to post it once I get it.
Well, once I was doing all the work on the SQL Server 2005 machine, I encountered an error doing the migration itself. It was complaining about DTC transactions. Then it hit me, that the same thing might be whats wrong with the migration to the SQL Server2008. So I added the following settings and voilá! it worked!
I did notice that they had info about this on their Migration tool info page but the error itself never came up when doing the migration, except when I tried to run it against SQL Server 2005.
Hope this helps someone out 😛