August 18, 2011 at 3:30 pm
Heh.... I actually take exception to anyone calling any import method other than SSIS a "band aid solution". Let me ask... can you execute two instances of the same SSIS package at the same time for parallel loading to save even more time? π
--Jeff Moden
Change is inevitable... Change for the better is not.
August 18, 2011 at 4:09 pm
Apologies, Jeff!
I was most definitely referring to my solution of trying to squeeze the out dated OPENROWSET into the 64 bit environment when mentioning band-aid π
August 18, 2011 at 4:59 pm
dji (8/18/2011)
Apologies, Jeff!I was most definitely referring to my solution of trying to squeeze the out dated OPENROWSET into the 64 bit environment when mentioning band-aid π
Understood and thank you for getting back to me. π
If I understand correctly, though, most folks I know say that SSIS won't import "text qualified" files (files with double quotes in them if a delimiter, such as a comma, is present in a given field of the file. It's also my understanding that the new "ACE" (a "replacement for the JET drivers) will and that it works just fine using OPENROWSET. Knowing that, I'm not quite ready to call OPENROWSET or similar technologies "outdated". π
--Jeff Moden
Change is inevitable... Change for the better is not.
August 18, 2011 at 5:12 pm
Jeff Moden (8/18/2011)
dji (8/18/2011)
If I understand correctly, though, most folks I know say that SSIS won't import "text qualified" files (files with double quotes in them if a delimiter, such as a comma, is present in a given field of the file.
You are correct. If you have the same character in a column as the delimiter the package crashes.
You have to use an ANSI character that a user would never enter.
SSIS is a good ETL tool but if there is an alternative that takes less time to develop or executes faster then it is a better solution.
For better, quicker answers on T-SQL questions, click on the following...
http://www.sqlservercentral.com/articles/Best+Practices/61537/
For better answers on performance questions, click on the following...
http://www.sqlservercentral.com/articles/SQLServerCentral/66909/
August 18, 2011 at 6:10 pm
Welsh Corgi (8/18/2011)
Jeff Moden (8/18/2011)
dji (8/18/2011)
If I understand correctly, though, most folks I know say that SSIS won't import "text qualified" files (files with double quotes in them if a delimiter, such as a comma, is present in a given field of the file.
You are correct. If you have the same character in a column as the delimiter the package crashes.
You have to use an ANSI character that a user would never enter.
SSIS is a good ETL tool but if there is an alternative that takes less time to develop or executes faster then it is a better solution.
Thank you for the confirmation. Not being one to use SSIS, I wasn't 100% sure.
--Jeff Moden
Change is inevitable... Change for the better is not.
August 18, 2011 at 11:11 pm
Jeff Moden (8/18/2011)
dji (8/18/2011)
Apologies, Jeff!I was most definitely referring to my solution of trying to squeeze the out dated OPENROWSET into the 64 bit environment when mentioning band-aid π
Understood and thank you for getting back to me. π
If I understand correctly, though, most folks I know say that SSIS won't import "text qualified" files (files with double quotes in them if a delimiter, such as a comma, is present in a given field of the file. It's also my understanding that the new "ACE" (a "replacement for the JET drivers) will and that it works just fine using OPENROWSET. Knowing that, I'm not quite ready to call OPENROWSET or similar technologies "outdated". π
This would be a BIG problem for me, fortunately the data is not quite so bad that my particular text qualifier " is contained in any of the text fields.
I was unaware of any 'working' replacement for the JET drivers, I have read of developers who were able to get something working with OPENROWSET but I never managed to get it working despite downloading and intsalling everything I read on various 'work-arounds' posted on different forums. The SSIS solution I have for looping through a directory is very simple and many times quicker than using openrowset from within a vb.net programme to achieve the same results. At my time of desperation it seemed as though the rug had been well and truly pulled from under the feet of anyone using OPENROWSET, and now I have discovered SSIS I would hate to go back to the dark days when MS simply decide on a whim to stop supporting a particular technology leaving many people high and dry, hopefully this won't happen anytime soon with SSIS.
August 18, 2011 at 11:29 pm
dji (8/18/2011)
Jeff Moden (8/18/2011)
dji (8/18/2011)
Apologies, Jeff!I was most definitely referring to my solution of trying to squeeze the out dated OPENROWSET into the 64 bit environment when mentioning band-aid π
Understood and thank you for getting back to me. π
If I understand correctly, though, most folks I know say that SSIS won't import "text qualified" files (files with double quotes in them if a delimiter, such as a comma, is present in a given field of the file. It's also my understanding that the new "ACE" (a "replacement for the JET drivers) will and that it works just fine using OPENROWSET. Knowing that, I'm not quite ready to call OPENROWSET or similar technologies "outdated". π
This would be a BIG problem for me, fortunately the data is not quite so bad that my particular text qualifier " is contained in any of the text fields.
I use SSIS extensively but it's not made of magic pixie dust as some have touted. It is perfect from far, but far from perfect π
SSIS actually makes use of OPENROWSET under the covers in some scenarios too. I am still not sure why the dev team could not get CSV support "right". IMHO it's borderline unforgivable and I have seen it be a barrier to adoption.
At any rate, I am happy you found a working solution, and a new toy it seems π All my gripes aside, SSIS is definitely worth the effort to get to know. Good luck!
There are no special teachers of virtue, because virtue is taught by the whole community.
--Plato
August 19, 2011 at 2:04 am
dji (8/18/2011)
... and many times quicker than using openrowset from within a vb.net programme to achieve the same results
Heh... just about anything is faster than that. Why on Earth would you even get vb.net involved with OPENROWSET? Certainly not to get a simple list of files... π
EXEC master.dbo.xp_DirTree 'C:\Windows', 1, 1
--Jeff Moden
Change is inevitable... Change for the better is not.
August 19, 2011 at 2:31 am
Jeff Moden (8/19/2011)
dji (8/18/2011)
... and many times quicker than using openrowset from within a vb.net programme to achieve the same resultsHeh... just about anything is faster than that. Why on Earth would you even get vb.net involved with OPENROWSET? Certainly not to get a simple list of files... π
EXEC master.dbo.xp_DirTree 'C:\Windows', 1, 1
oh:blush:
Is there a big overhead using vb.net --> SQL?
August 24, 2011 at 6:54 pm
Sorry... lost track of this post.
Maybe, maybe not. "It Depends" on how the VB is written. But, personally, I'd rather just use the xp_DirTree thing because if I can keep things in T-SQL, I don't need to worry about where source code is stored. π
--Jeff Moden
Change is inevitable... Change for the better is not.
August 25, 2011 at 7:20 am
SSIS have no problem with large files. I use it to import cvs files about 7G every day (6 millions rows) and have no problem.
-
Lic. AndrΓ©s M. Aiello
DBA MSSQL - Oracle
August 25, 2011 at 10:40 am
Aiello DBA (8/25/2011)
SSIS have no problem with large files. I use it to import cvs files about 7G every day (6 millions rows) and have no problem.-
Lic. AndrΓ©s M. Aiello
DBA MSSQL - Oracle
How long did the 6 million rows take?
--Jeff Moden
Change is inevitable... Change for the better is not.
August 25, 2011 at 10:46 am
About 5 and a half hours. Was a firewall log monitoring all pcs information about internet.
-
Lic. AndrΓ©s M. Aiello
DBA MSSQL - Oracle
August 25, 2011 at 4:14 pm
Any idea how long it would take without the firewall monitoring? The reason I ask is that I've seen BULK INSERT import 5.1 million, 20 column rows from a CSV file in a minute flat.
--Jeff Moden
Change is inevitable... Change for the better is not.
Viewing 14 posts - 31 through 43 (of 43 total)
You must be logged in to reply to this topic. Login to reply