I was able to create a new table using the import/export wizard. The wizard was nice as it created the correct columns needed in order to hold the unicode data. I have read that SQL Server stores unicode in UCS-2 encoding schema, and the source was UTF-8. So, I'm unsure if there will be issue there. Has anyone taken this approach? Will the difference between encodings cause issues?