February 19, 2016 at 12:45 pm
we have a table from Oracle that has millions of records. We have a query to get from that table and into SQL server staging table. I would like to import either all the columns, or only the columns I use in SQl server queries.
I wonder if it reduces import time or not if I include few columns vs all the columns.
The reason I include all columns are for reference. But of course, I can always go to oracle db to check those columns if for further information.
But if it increases time significantly I would rather just import those needed columns.
Any suggestions.
Thanks,
February 19, 2016 at 12:51 pm
sqlfriends (2/19/2016)
we have a table from Oracle that has millions of records. We have a query to get from that table and into SQL server staging table. I would like to import either all the columns, or only the columns I use in SQl server queries.I wonder if it reduces import time or not if I include few columns vs all the columns.
The reason I include all columns are for reference. But of course, I can always go to oracle db to check those columns if for further information.
But if it increases time significantly I would rather just import those needed columns.
Any suggestions.
Thanks,
The number of columns you import does affect processing time. Import only those which you require to optimise the process.
Viewing 2 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply