Viewing 15 posts - 9,346 through 9,360 (of 13,874 total)
KoldCoffee (3/24/2014)
regarding prior reply about Unicode - I'm not getting error pertaining to Unicode/non-Unicode and 80,000 rows ARE transferring.How would I determine if it's line terminators?
So does it always fail...
March 25, 2014 at 4:48 am
aaron.reese (3/24/2014)
yup. You might need to use a script component or WMI. Here are a couple of linkshttp://www.bidn.com/blogs/mikedavis/ssis/157/ssis-wmi-event-watcher-check-file-exist-creation
http://www.bidn.com/blogs/DevinKnight/ssis/76/does-file-exist-check-in-ssis
Use a Script Task, not a Script Component.
Here's a C# snippet...
March 25, 2014 at 1:09 am
We don't use this tool, but it promises to do at least some of what you are looking for:
http://www.embarcadero.com/products/er-studio-data-lineage
Not free though ...
March 25, 2014 at 1:05 am
Informer30 (3/24/2014)
OK thanks -confused how csv files work then, they are flat files but unable to open in a csv viewer?
A CSV file is just a structured text file. Nothing...
March 24, 2014 at 11:29 am
No. How are you viewing the CSV? Use a decent text editor, not Excel.
March 24, 2014 at 8:59 am
Koen Verbeeck (3/24/2014)
aaron.reese (3/24/2014)
Next question. Which files need to be in SCC and which...
March 24, 2014 at 3:55 am
Or maybe let SSIS do all the work by defining @@@ as a column delimiter.
March 24, 2014 at 1:57 am
You could potentially create a SQL Agent job to run the package and then allow the user to start that job.
March 24, 2014 at 1:36 am
aaron.reese (3/21/2014)
Looked at the package in XML and the fields being reported in the errors only exist once.
Sounds like you have some corruption in your package. (Nasty! Call a doctor!...
March 21, 2014 at 5:23 am
You could try opening the package in an XML editor and looking for the offending GUID - might give you some clues.
March 21, 2014 at 4:27 am
aaron.reese (3/21/2014)
March 21, 2014 at 3:28 am
elee1969 (3/20/2014)
March 20, 2014 at 12:02 pm
Eric Mamet (3/20/2014)
March 20, 2014 at 6:00 am
I presume this is because you may have multiple occurrences of the 'new' lookup item in your source data and you don't want to risk creating something which is already...
March 20, 2014 at 5:45 am
declare @XML as xml
set @XML = '<?xml version=''1.0'' encoding=''UTF-8''?><root available-locales="en_GB" default-locale="en_GB"><Title language-id="en_GB">Cookies</Title></root>'
select @XML.value('(root/Title)[1]', 'varchar(50)')
March 20, 2014 at 5:36 am
Viewing 15 posts - 9,346 through 9,360 (of 13,874 total)