Viewing 15 posts - 13,006 through 13,020 (of 13,877 total)
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
If you can get just a bit more specific, I think we can help you.
What do you mean by 'validate'? Is there a certain column that always has a certain...
February 3, 2009 at 5:25 am
For one solitary piece of data it's certainly a pain - but if you are generic about how you write it you will be able to reuse in future.
Phil
February 2, 2009 at 7:17 pm
Not really. You might consider creating a physical 'Variables' table in SQL Server and using that to store/lookup any variables which are truly global.
Phil
February 2, 2009 at 7:06 pm
That's not a great error message:) Maybe it should just have said: "Something, somewhere, is wrong."
I just tried one on my system. Try this:
Resultset = None
SQLSourceType = Direct Input
SQL Statement...
February 2, 2009 at 6:35 pm
I suggest that you concentrate on getting the sp working fast on its own without worrying about SSIS for now.
You should try to work out where the bottleneck is: is...
February 1, 2009 at 7:37 pm
Add an Execute SQL task. Set the appropriate Connection info, then set the SQL Statement property to
EXEC sp_name
where sp_name is the name of your stored proc.
Phil
February 1, 2009 at 7:30 pm
Viewing 15 posts - 13,006 through 13,020 (of 13,877 total)