Bytes and Bites of Internet
Posts tagged Migration
Moving wordpress blog across Domains and Hosts …Yet another migration !!
Dec 29th
And finally after using free hosting / with free domain service for my blog, I finally thought to move to more “professional” place because my current free service limits me to number of files I can create !! and honestly, like any free lunch that doesn’t taste good … my domain name was sucker 🙂 … which was kind of main reason (though hosting and domain name has nothing in common) to move my blog here.
It is not that much of painful process as I was expecting in the beginning. Almost everything went seamless, so I am gonna write about it in this post.
NOTE: As being user of Computer you already know that for any given problem in computer “mostly” we have more than one solution. Same thing is for this migration process, it can be done more than one way. Here described process is what I have followed, but you may find more suitable method on somewhere else too !!
Step 1: Being “IT Guy” (sounds goooooood) I know importance of having backup incase if you want to fall back at any give time. Or just coz of bad luck something goes wrong and you mess up with something in your wordpress setup you may want to have an option to rollback by restoring GOOD copy. So, firstly backup your whole DB and WP files. To take backup from your WP database, the easy way was to login to phoMyAdmin app in my cPanel to WP Database. Once in go to select “Export” tab and make sure all tables have been selected and type is SQL.
Access to SQL Server migration … and Compatibility Issues !!
Oct 7th
Recently I was involved in a migration project. Client was/is using ancient application built on Access 2.0 (yup … its 2.0) … I think it was started as a small app for just couple of users and with time it grew larger and soon it became mission critical application which still is built on old technology. Now here I am not gonna discuss about advantages of SQL Server over Access … because fact is both have their place in Data Processing Systems. In my native language we have a nice saying which loosely means that “sometimes we can’t do something by knife, that has to be done by needle” … having little bit interest in element of life and Zen … I consider myself self-proclaimed philosopher 
, ( if you have problem with that then … I really don’t care ) … oki back to discussion … what I meant to say is, in a situation where you need very small application that will be used by 1-2 or very few people, with very little data to process (v2.0,95,97 everyone had 1GB physical size limit), have very little or no budget, easy to maintain,deploy and design solution then I guess access is pretty good fit. But if there are high number of concurrent users (user > 5-10), high data storage capacity, requirement of better ( wayyy better ) security then SQL Server is ideal solution.
With that said, let me explain the situation that let me to write this blog post. I had already installed, patched and configured SQL Server properly on our database server, I had also prepared the workstation too, which was able to connect to database server. Now, I thought to try for test run of a sample migration. It was an access 97 file (which was originally access 2.0, converted to access 97 to be compatible with SQL Server import.) with just 2 database and had no other stuffs (or say views). I first opened that access file in my workstation to be sure that it is working (I mean not corrupted), after that I fired up SQL Server Migration Assistance (SSMA, is a great free utility by Microsoft which allows users to migrate access database to SQL Server, which can also be done by making package in SSIS).
And I was greeted with this message in SSMA console …
Starting conversion... Analyzing metadata... Access Object Collector error: Database Retrieving the COM class factory for component with CLSID {CD77B9-4FD-42C5-AE42-8D281F0419} failed due to the following error: 80040154. This error may be a result of running SSMA as 64-bit application while having only 32-bit connectivity components installed or vice versa. Please run SSMA in 32-bit (or 64-bit) mode or consider updating your connectivity components from http://go.microsoft.com/fwlink/?LinkId=197502. An error occurred while loading database information. Conversion finished with 0 errors, 0 warnings, and 0 informational messages. There is nothing to process.