j.bluestein (3/13/2013)

---

thanks for the replies, I've attached the properties of the sell descr it is 30 character long...

glad to hear you've loaded the file and your table has that...

 is a valid ANSI character as far as SSIS and SQL Server are concerned, Latin1 codepoint 194 to be exact. Truncation could mean that the string length exceeds what...

If the data source is a file and its failing in SSIS then SQL is not going to help you unless you can get the data from the file into...

I see it. Change this:

RowNum = ROW_NUMBER() OVER (PARTITION BY Software_Name_Raw ORDER BY Software_Name_Raw),

to

RowNum = ROW_NUMBER() OVER (PARTITION BY Software_Name_Original ORDER BY Software_Name_Original),

Hopefully this is not the case in anyone's environment as shrinking tempdb is a risky thing to do and there...

Yeah, we can get distracted delving too far into the details 😀

...will it be a definate that...

No bother at all. Happy you got it sorted.

Chrissy321 (3/12/2013)

---

Thank you for responding to my narrative.

Yes I am using xp_cmdshell. I get the same error when I add the SQL Server service account to the sysadmin, that...

COALESCE too...

The base column would, as I understand it, always come across as-is in terms of it's NULL/NOT NULL property if selected straightaway in a SELECT...INTO. By 'not copying NULLability' I...

You can in 2008 and up, and maybe in later service packs of 2005, but in any case you may not want to do that. In 2005, and in some...

Eugene Elutin (3/12/2013)I agree that there is no rule of thum for using SELECT ... INTO over INSERT ... SELECT, however I always start with SELECT ... INTO before considering...

That's my understanding as well. All memory allocation is now coming from the same allocator and the best known side-effect of that change is that the 'max server memory' option...

I could find nothing in my 2008 Internals book (Delaney) that would explain the difference. The differences are odd but are nothing that I expect will ever affect how I...

It...