Viewing 15 posts - 31 through 45 (of 47 total)
First question..having trouble using the for loop container against the excel spreadsheets. Could you provide more detail like an error it's throwing? Not enough info to go on...
February 13, 2008 at 2:24 am
Common problem, unfortunately this is the way it's meant to work (ie. you can only identify one problem column at a time.
One method that might be worth considering depending on...
February 13, 2008 at 2:15 am
Good advise above, I would recommend you use the for each looping container to break each segment of data out into separate csv files.
Basically it would go like...
February 13, 2008 at 1:43 am
A few add-ons to the previous post...
1.) While running the package with in BIDS ensure you set the package to run in optimized mode. This can be useful...
December 21, 2007 at 1:28 pm
Several ways to skin that cat,
An easy one would be to use the Derived column task between the Source and Destination tasks. Have it create a new column and...
December 21, 2007 at 12:56 pm
Hey there,
Fuzzy Group by design is very resource intensive. However, there are a few general things you can do to ease up on the problem of performance.
1.) Make sure...
December 21, 2007 at 12:35 pm
Make sure I have this correct...It run's great from your local desktop where you put it together, but if you deploy it to the SQL Server and run it under...
December 21, 2007 at 12:13 pm
If your executing this through expressiong you need to ensure that double your quotes or it will throw a syntax error. So UNC path of \\servername\mydir\myfile.txt would actually need...
December 21, 2007 at 12:09 pm
If one of the columns in the dataset holds a key or date that is repeated you can use the SORT transformation. Set the sort on the key field,...
December 21, 2007 at 11:56 am
Hey There,
It's pretty straight forward.
Drag the task into your package and link via the correct precedents if needed.
Right click the Task and choose Edit.
Under the General give...
December 21, 2007 at 11:51 am
Is your only goal to off load the overhead of SSIS from your production SQL Server (where your applications live)? If so you could simplify your problem by running...
December 21, 2007 at 11:35 am
This is a common problem. The SQL Agent needs to have ownership of the package before it can run it as a job. Since you created it on...
December 21, 2007 at 11:14 am
One idea would be to convert the float value to a big string to ensure no matter what the value is it will fit. Then the derived column transformation to...
December 21, 2007 at 11:08 am
Probably the simplest way to accomplish this would be to add the DateColumn in the SQL table your importing to, set the default value for the column to GETDATE(), on...
December 21, 2007 at 10:58 am
Viewing 15 posts - 31 through 45 (of 47 total)