Since installing SP1 for SQL 2012 on my workstation, the import/export tasks from SSMS no longer recognize the varchar and nvarchar fields:
CREATE TABLE [dbo].[TestTable]( [ID] [int] IDENTITY(1,1) NOT NULL, [VariableCharacterField] [varchar](50) NULL, [UnicodeVariableCharacterField] [nvarchar](50) NULL, [DateTimeField] [datetime] NULL, [DateField] [date] NULL, [TimeField] [time](7) NULL, [BitField] [bit] NULL, [BigIntField] [bigint] NULL, [CharacterField] [char](50) NULL, [UnicodeCharacterField] [nchar](50) NULL, [BinaryField] [binary](50) NULL, [DecimalField] [decimal](18, 0) NULL, [FloatField] [float] NULL, CONSTRAINT [PK_TestTable] PRIMARY KEY CLUSTERED ( [ID] ASC )WITH (PAD_INDEX = OFF, STATISTICS_NORECOMPUTE = OFF, IGNORE_DUP_KEY = OFF, ALLOW_ROW_LOCKS = ON, ALLOW_PAGE_LOCKS = ON) ON [PRIMARY] ) ON [PRIMARY]
The destination is a table that does not exist on another SQL 2012 database. I've also noticed that it changes nchar to nvarchar, binary to varbinary, datetime to datetime2, and time to sql_variant.
The same thing from an installation of SSMS that does NOT have SP1:
It seems whatever detects the data types in SP1 when SQL Server Import/Export Wizard is launched from within SSMS is not correctly identifying the data types, and in the case of nvarchar/varchar, results in garbage.