Hi Guys, When I create a package that loads data from oracle 11g to SQL Server 2008 R2 X64 by using the wizard it performs perfectly. I then try to change the package in bids to use my shared data sources. no problem when changing source connection. But when i try to change the destination OLEDB then it starts to perform very badly. I have tried running it with the from wizard defined destinationOLEDB and after changed in BIDS, there is a huge difference in performance. Any idea why this happens? I have even removed 64bit mode in debugging. Best Regards ElvisELVIS_OF_BI

Is it SQL Server 2005? Could be a problem with a driver.Best Regards, Uri Dimant SQL Server MVP http://dimantdatabasesolutions.blogspot.com/ http://sqlblog.com/blogs/uri_dimant/

Does the wizard use a different driver than your shared data source?MCTS, MCITP - Please mark posts as answered where appropriate.

Use ADO not OLEDBArthur My Blog

Is it SQL Server 2005? Could be a problem with a driver. Best Regards, Uri Dimant SQL Server MVP http://dimantdatabasesolutions.blogspot.com/ http://sqlblog.com/blogs/uri_dimant/ OP stated SQL Server 2008 R2 X64 so it's not SQL Server 2005Jeff Wharton MSysDev (C.Sturt), MDbDsgnMgt (C.Sturt) MCT, MCPD, MCITP, MCDBA, MCSD, MCAD

Hi Guys, Yes its SQL 2008 R2, the driver is exactly the same as the one I chose in the Wizard, i have seen there are some different settings that are set as default when creating the data source in the BIDS. But changing them to be exact the same does not help. First i thought it must be that the SQL driver is a 32bit in BIDS because bids is 32 bit but I tried to deploy the package and then tested it and still it performed very badly. Any ideas? I am using the SQL Server native connection, i also tried OLEDB for SQL server but the same result. Best Regards Elvis!ELVIS_OF_BI

Use ADO not OLEDB Arthur My Blog Did you try?Arthur My Blog

Use ADO not OLEDB Arthur My Blog I'm not sure this will fix it but I'm happy to be proven wrong :-)Jeff Wharton MSysDev (C.Sturt), MDbDsgnMgt (C.Sturt) MCT, MCPD, MCITP, MCDBA, MCSD, MCAD

I also believe in ADO.Net connection with bulk when possible option :). It helps. when comes to the actual problem. wizard is a light weight component. sorry, you have mentioned that you deployed and still slow :) Did try to change the Rowperbatch, table lock settings and other options in the ole db destination.Thanks Ayyappan Thangaraj UG Lead, Puducherry, http://SQLServerRider.blogspot.com