Well, to start, let me say…there are 100 and 32 flavors of things that you ’should’ know before outsourcing your software project to firms in other countries…here is a quick hitter of 8 major things to think about before jumping into the world wide web of deceptive software outsourcing.

My purpose here is to inform you about some of my experiences and not to necessarily bash these companies. I have done business with many good people overseas - and I have experienced some disasters. This post is to help you avoid some of the disasters.

  1. Experts are hard to find. In this day and age, everyone and their brother claims to be software developers. Do your research on the company you decide to go with- look at samples of their work. Experts are getting harder and harder to find. Ask lots of questions…and know what questions to ask.
  2. Do your homework. Know who you are doing business with.
  3. Fail to plan, plan to fail. You must be prepared to hold their hand. Document every little requirement before starting any coding and make sure to get everything in writing.
  4. Software companies don’t do design well - Don’t expect an outsourced technology/software company to do ‘design’ or UI work. (If you find a software company that can do great UI design, please let me know.)
  5. Don’t oversimplify your project. Even though “you” think that a your project is “easy,” you must be prepared and understand that, most likely - it WILL turn into a much larger project than you think. So when the developers come to you and say…its going to take another week to complete your website. Just be prepared. And again, planning ahead will help to reduce the likelihood of this happening.
  6. Everyone is in business to make money - outsourced software companies included. An upfront low ball price, in my experience, will only get you sucked into a long and drawn out project where they keep coming to you for money every month — while your application never seems to get completed. The lowest price is not always the best price.
  7. Communication. This is usually the #1 reason why project fail. Communicating, setting expectations, and then keeping your calm when they are not met. What is your preferred means of communication? Many of these companies prefer to use IM (instant messenger). Now, don’t get me wrong, IM is great for communicating but can you pick up the phone and call them if necessary? Better yet, do they speak the same language as you do? Just keep this in mind throughout the lifetime of your project.
  8. Business ethics. Yes. This does come into play. Now, there are plenty of companies out there that are “good” people, and I have worked with many. But on the flip side, there are also tons of companies that simply want your money. In the US, we are generally accustomed to ‘get what we pay for.’ But as the world is getting smaller and smaller, we have become a bit naive now. As things get sourced to other countries, you better watch your back…some of these people just don’t have the same ethics as we do. It’s your job to know what you are buying and receiving. Buyer beware.

Again, I would say that these are some of the top things to think about before going overseas, mainly to avoid the bad experiences, the grey hairs, the sleepless nights, the hand holding, and overall - to save you money in the long run.

{ 0 comments }

How to Restore a MSSQL 2005 Database

by Tim Eisenhauer on November 7, 2008


Restoring a MSSQL 2005 database can be hell for those that do not know how to do it properly. Espically if you are restoring this database on a different server than what it was created on.

I have watched developers spend hours on this simple but trivial task. And I, at times, have even found myself spending entirely way too much time tryting to restore a backup. It’s one of those tasks that pops up (for me anyway) only a few times a year. So, to save time, I thought it would be helpful to document the process.

Now, if there is something I missed, or if there is a better way of doing this, please let me know. Thanks, and good luck.

Oh, and just for your reference, and if you want to sift through the ocean of info - Microsoft explains it here

Restoring a MSSQL 2005 Database
(to a database on a different server)

  1. copy your .bak file to: C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Backup
  2. Most likely, the security permissions should be sufficient however there are times when I run into security issues. So I simply right click on the .bak file and on the security tab, I go through the process and add ‘everyone’ to have complete acess to the .bak file.
  3. Launch Microsoft SQL Management Studio.
  4. Create a new database - This will create a .mdf and a .ldf in this directory: C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Data
  5. In the SQL Server manager Object Explorer, right click on Databases and choose “Restore database…”
  6. This will open the “Restore Database” window.
  7. Under “Destination for restore” and then in the “To database” pulldown, choose the database that you created in step 4.
  8. Under “Source for restore” click the “From device” radiobutton, then click the browse option. This will open a window to “Specify Backup”. Click “Add” then navigate to the path where you put your .bak file (C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Backup). Choose your .bak file and click “OK”, then “OK” agian.
  9. You should now see your backup file loaded in the grid. Click the checkbox next to your backup.
  10. Then in the right column of this window, click options.
  11. First, click the checkbox “Overwrite the existing database”
  12. Now, you have to set the location of the .mdf and .ldf you want to restore. Remember when you created the new database in step 4 - and it created a new .mdf and .ldf? Well, these are the two files you want to restore. You should see at the least, two rows in the grid (under “Restore the database files as”). The first one should be the name of the database you are restoring, and the second one will probably end in “_log”.
  13. Click the browse option for the first File name. Then navigate to .mdf file you created in step 4. (C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Data) Click the .mdf file you created and then click “OK”
  14. You are going to repeat the same process for the next item in the grid (ending with _log). Click the browse option for the second File name. Then navigate to .ldf file you created in step 4. (C:\Program Files\Microsoft SQL Server\MSSQL.1\MSSQL\Data) Click the .mdf file you created and then click “OK”
  15. After doing all of the above steps, you should be ready to rock and roll. Click the “OK” button and the backup should begin.

Obviously, if you get a “success” message, the backup worked. If you get an “error” message…well, try try again.

{ 0 comments }

John Butler - Ocean

by Tim Eisenhauer on November 4, 2008

Now, this gets the blood flowing…amazing guitarist.

{ 0 comments }

Hello World! This is the second post!

by Tim Eisenhauer on October 30, 2008


Integer arcu tellus, mattis quis; tempus sit amet, aliquam id, leo? Vestibulum tincidunt metus eget nulla. Aenean mollis tortor quis lorem? Phasellus et velit! Cras vel risus eget nunc accumsan ultrices. Quisque dui. Proin purus ante, fermentum sit amet, consectetuer ut, suscipit eu, purus. Mauris viverra suscipit risus. Vivamus malesuada metus eu turpis. Aenean adipiscing rutrum leo.

Your note text goes here!

Etiam nec lectus. Proin enim felis, vestibulum sed, consectetuer vel, dapibus in; metus? Praesent massa tortor, mattis at, dictum dignissim, molestie vitae, nisl! Pellentesque consequat metus venenatis neque? Aliquam tempus. Curabitur eu dolor! Duis laoreet. Fusce dui est, posuere et, facilisis et; cursus nec, odio. Sed mollis augue at lacus. Aliquam dapibus. Donec accumsan. Duis est pede, congue in, tristique at, tincidunt sed, libero? Nullam urna. Ut vel sapien. Aenean fringilla ultricies nisl.

Your alert text goes here!

Ut egestas dolor adipiscing sem. Nam diam est, ullamcorper a, bibendum vitae, blandit pellentesque, augue. Vestibulum vitae eros. Phasellus vel pede ac quam tincidunt hendrerit. Praesent magna nunc, convallis ut; sagittis vitae, aliquet nec, massa. Aenean in dolor. Vivamus sed nibh non quam egestas elementum. Integer tellus mauris, tempus vel, adipiscing ac; volutpat in, tellus. Sed ac ante. Donec quis risus non est blandit sollicitudin. Fusce erat orci, pretium ut, rhoncus ut; porta non, nibh. Nam convallis bibendum nulla!