Is anyone using this currently?
I'm having major issues transitioning our 2000 DTS packages over to 2005, 2005 just doesn't seem to want to import the data, bugging out every time with the error:
"cannot convert between unicode and non-unicode string data types."
In fact, I get the exact same error trying to do it from scratch with the import wizard to create a brand new SSIS package.
This is the data file I'm trying to import, it's vertical bar delimited, with mac style {cr} only row delimiters (this isn't an issue at all in SQL Server 2000).
This is the table it goes into:
Am I correct in thinking that 2005 is being far more specific with it's table formatting, which is then causing an issue when I try to import that data into the existing table?Code:[ID] [int] IDENTITY(1,1) NOT NULL, [SiteCode] [nvarchar](50) COLLATE Latin1_General_CI_AS NULL, [SiteName] [nvarchar](50) COLLATE Latin1_General_CI_AS NULL, [SiteType] [nvarchar](50) COLLATE Latin1_General_CI_AS NULL, [Country] [nvarchar](50) COLLATE Latin1_General_CI_AS NULL, [Region] [nvarchar](50) COLLATE Latin1_General_CI_AS NULL, [Area] [nvarchar](50) COLLATE Latin1_General_CI_AS NULL, [County] [nvarchar](50) COLLATE Latin1_General_CI_AS NULL, [Place] [nvarchar](50) COLLATE Latin1_General_CI_AS NULL, [PageNumber] [nvarchar](50) COLLATE Latin1_General_CI_AS NULL, [SiteDesc] [ntext] COLLATE Latin1_General_CI_AS NULL, [SiteFeatures] [ntext] COLLATE Latin1_General_CI_AS NULL, [Airport] [nvarchar](50) COLLATE Latin1_General_CI_AS NULL, [Note] [ntext] COLLATE Latin1_General_CI_AS NULL, [VTEnabled] [nvarchar](50) COLLATE Latin1_General_CI_AS NULL, [IndoorOutdoor] [nvarchar](80) COLLATE Latin1_General_CI_AS NULL, [IO_Text] [ntext] COLLATE Latin1_General_CI_AS NULL, [SpecialHead] [nvarchar](80) COLLATE Latin1_General_CI_AS NULL, [SpecialText] [ntext] COLLATE Latin1_General_CI_AS NULL


LinkBack URL
About LinkBacks
Reply With Quote
