If he's using an SSIS package to transfer the data it is probably about as simple as it can get, most of our SSIS packages have no lines of code at all. Just point and click data flows like a lot of powerful ETL packages on the market.
Not only is it easier to transfer data with SSIS it also is a self-describing workflow that doesn't require you to print pages of RPG or .NET code that does the same thing. Instead you end up with easy to read data flows like this:
http://i.msdn.microsoft.com/dynimg/IC144458.gif or more complicated data flows like this:
http://social.msdn.microsoft.com/Forums/getfile/133440
Sean, what were the results of changing the package encryption level as I had suggested in the previous postings?
-----Original Message-----
From: Richard Schoen [mailto:richard@xxxxxxxxxxxxxxx]
Sent: Thursday, February 21, 2013 11:07 PM
To: midrange-l@xxxxxxxxxxxx
Subject: RE: Microsoft Integration Services password
Confusion abounds :-)
Based on my understanding of your needs I was advocating having an RPG program front end the SQL Server.
In other words. RPG Read/Write to SQL Server as a Client as needed.
No more DTS and no .Net programming or PC side scripting needed.
Regards,
Richard Schoen
RJS Software Systems Inc.
Where Information Meets Innovation
Document Management, Workflow, Report Delivery, Forms and Business Intelligence
Email: richard@xxxxxxxxxxxxxxx
Web Site:
http://www.rjssoftware.com
Tel: (952) 736-5800
Fax: (952) 736-5801
Toll Free: (888) RJSSOFT
------------------------------
message: 6
date: Thu, 21 Feb 2013 23:42:39 -0500
from: "Porterfield, Sean" <SPorterfield@xxxxxxxxxxxxxxxxxxxxxxx>
subject: RE: Microsoft Integration Services password
My comment about in place data was a reply to your comment about in place data. It sounded like you were suggesting not transferring data to the SQL Server, rather having it just read the data it needed from the IBM i when it needed it.
--
Sean Porterfield
________________________________________
From: midrange-l-bounces@xxxxxxxxxxxx [midrange-l-bounces@xxxxxxxxxxxx] On Behalf Of Richard Schoen [richard@xxxxxxxxxxxxxxx]
Sent: Thursday, February 21, 2013 14:54
To: midrange-l@xxxxxxxxxxxx
Subject: RE: Microsoft Integration Services password
Keep in mind to test all scenarios with ArdGate as well if you go down that road.
I have been able to freeze up that engine when playing with it.
Mileage will vary with any tool even ours :-)
PS: I didn't understand your previous comment in regards to in place data. Using ArdGate, Scotts JDBC Method, our RPG2SQL or whatever you use for DB access are all essentially the same methodology if you are reading or writing data records. Hmmmm :-) ?
Regards,
Richard Schoen
RJS Software Systems Inc.
Where Information Meets Innovation
Document Management, Workflow, Report Delivery, Forms and Business Intelligence
Email: richard@xxxxxxxxxxxxxxx
Web Site:
http://www.rjssoftware.com
Tel: (952) 736-5800
Fax: (952) 736-5801
Toll Free: (888) RJSSOFT
------------------------------
message: 3
date: Thu, 21 Feb 2013 13:09:47 -0500
from: "Porterfield, Sean" <SPorterfield@xxxxxxxxxxxxxxxxxxxxxxx>
subject: RE: Microsoft Integration Services password
Reading/inserting a record at a time is a process my mind can grasp, but I suspect the performance would be abysmal given the volume of data.
I had forgotten about ArdGate until after I posted. I was thinking about that more when I still couldn't sleep. Part of the future design will be to allow an end user to resubmit the build job with selection criteria, so having a server process in place will make a lot of sense, rather than having Java running in the user's job.
--
Sean Porterfield
-----Original Message-----
From: Gary Thompson
I have no experience that compares with your .3M to 1M rows, but my guess is you will need to do serious performance testing.
We looked at ArdGate which is open source available on SourceForge.net
- I found a lot to
This email is confidential, intended only for the named recipient(s) above and may contain information that is privileged. If you have received this message in error or are not the named recipient(s), please notify the sender immediately and delete this email message from your computer as any and all unauthorized distribution or use of this message is strictly prohibited. Thank you.
------------------------------
--
This is the Midrange Systems Technical Discussion (MIDRANGE-L) digest list To post a message email: MIDRANGE-L@xxxxxxxxxxxx To subscribe, unsubscribe, or change list options,
visit:
http://lists.midrange.com/mailman/listinfo/midrange-l
or email: MIDRANGE-L-request@xxxxxxxxxxxx Before posting, please take a moment to review the archives at
http://archive.midrange.com/midrange-l.
End of MIDRANGE-L Digest, Vol 12, Issue 422
*******************************************
midrange.com
