Viewing 15 posts - 12,961 through 12,975 (of 13,838 total)
40 connection managers - I do not envy that at all :doze:
But the alternative is to script it all and that is not nice either!
There are so many different files...
February 18, 2009 at 9:39 pm
There is an Import/Export Wizard which uses SSIS, instead of DTS.
Just right-click your db in SSMS and select Tasks / Import (or Export) data.
That should get you started.
Phil
February 18, 2009 at 6:33 pm
If you create variables to hold the source filename and destination filename, this becomes a piece of cake, as all you have to do is set the 'IsSourcePathVariable' and 'IsDestinationPathVariable'...
February 12, 2009 at 5:57 pm
An alternative approach would be for you to add a 'Rename File' task at the front of your package to rename the Access db to be the simple, static name...
February 10, 2009 at 6:30 pm
If (for testing purposes only) you use a simpler package which has an explicit name for the Access db, does it work? I would guess not, but it would be...
February 9, 2009 at 6:06 pm
stricknyn (2/7/2009)
I think you are referring to the script task not script component. The script task (control flow item) lets you debug. The script component (data flow item)...
February 7, 2009 at 2:01 pm
Could it be that the columns are being interpreted as numeric (because the first few rows of data contain numbers in those columns)? If so, when the non-numeric data is...
February 6, 2009 at 7:44 pm
I do this all the time - just set a breakpoint where you want to start debugging and then run it ...
Phil
February 6, 2009 at 7:39 pm
Sometimes it's easier just to accept that something works, rather than trying to understand why 🙂
Now you can move on to the next project: migration of DataEase data to SQL...
February 5, 2009 at 5:35 am
Just edit the Connection objects in each of the packages to have a Data Source ID of 'DWH_Staging' or 'JEDB' to create the link. Change to the Data Source will...
February 4, 2009 at 11:43 pm
You have made a statement, not asked a question. What do you want?
Also, you speak of DTS, yet you are posting in the SSIS forum. They are not the same...
February 4, 2009 at 10:39 pm
That does seem strange.
Is it the number of records imported (13,194), or a certain 'rogue' record that is causing the problem?
If you import the records into Access first (so that...
February 4, 2009 at 7:15 pm
Robert Ham (2/3/2009)
You can also pass variables from a parent package that uses the execute package task to run a child package.
So multiple child packages can read/write the same 'parent'...
February 3, 2009 at 11:09 pm
Scoping of variables at global or 'solution' level is not possible - so you have to find another way.
One way is to create a physical 'variables' table in SQL Server...
February 3, 2009 at 6:46 pm
This is how I would do it - no scripts required:
1) Create a new SQL Server table to hold the Access data temporarily (tblAS).
2) Write a stored proc on SQL...
February 3, 2009 at 5:33 am
Viewing 15 posts - 12,961 through 12,975 (of 13,838 total)