JWColby
jwcolby at colbyconsulting.com
Wed May 2 11:29:55 CDT 2007
>Good luck. Thanks, I appreciate that. I have in fact already solved my problem, just not within the confines of SQL Server. My solution is FAR from optimal but it does work and I am able to use it to get the job done. I have no doubt that SQL Server does indeed have capabilities that I cannot even begin to grasp, never mind make use of. One of the unfortunate problems that we all have is that MS proselytizes about how great and easy their tools are to use. I see that in Access, and understand exactly how far that is from the truth when it comes to anything other that the trivial. OTOH wizards are intended for the novice and should IMHO offer more than trivial solutions to trivial problems. As an example they have an AWSOME wizard for getting data into SQL Server. It allows you to use the wizard to import CSV files quickly and easily, and it even allows you to import fixed width files, though certainly not so quickly and easily, particularly when there are LOTS of fields. Having spent so much (programming) time on this wizard, how much extra time would it take to allow the stuff you entered to be stored (it does that) but more importantly REUSED BY THE WIZARD? They store this fixed width (import) stuff out to an SSIS file and then the silly (if quite powerful initially) wizard can't even read that file. AND the file itself is useless for the next pass because it has embedded in it stuff about creating a table (which was already created by the wizard during the first pass). AND it defaults to NVARCHAR which I for one don't need (it doubles the store size of my data - which is already HUGE). AND it offers no obvious way to say use VARCHAR instead. AND it (the import spec) is stored in XML which just SUCKS for trying to edit without a special tool. AND when clicked on (to edit it) it takes me to another tool entirely (VSS 2005) where it displays it graphically as objects to be edited but does NOT allow you to edit the pieces needed easily. Do you sense my frustration? Yea, SQL Server is an awesome tool. I BELIEVE THAT. But I am earning below minimum wage here spending HOURS and HOURS struggling to do the simplest damned thing, and in the end (having REALY AND TRULY spent hours and hours trying to get a handle on this) going back to my TOYS to get the job done. What the hell good is SQL Server 2005 Express going to do for (ME) Joe Blow developer (which MS is pushing it for) if what should be the simplest part is so damned complex that they (Microsoft) can't even build a wizard that will allow us to use it? Unfortunately, with terabyte sized databases to get input I do not have the option of throwing up my hands and going back to my toys. I must and will cope with the inanities. And if I vent, well... I apologize in advance. Having been on the ACCESSD list for so long, and seeing the skill level there, I had high hopes that I could get answers to this (apparently not so simple) problem on the SQL Server forum. Not to worry, I will survive, although minimum wage makes my house payment tough to make. John W. Colby Colby Consulting www.ColbyConsulting.com -----Original Message----- From: dba-sqlserver-bounces at databaseadvisors.com [mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of David Lewis Sent: Wednesday, May 02, 2007 11:20 AM To: dba-sqlserver at databaseadvisors.com Subject: Re: [dba-SQLServer] Bulk insert (Arthur Fuller) Hi Guys: Keep cool, everybody. John: The fact that you asked many questions that nobody here could answer is unfortunate but again doesn't reflect badly on the tool or the users. The two sites I mentioned (sqlcentral.com and sswug) have very active forums specifically dedicated to such topics as SSIS in 2005 or DTS in sql2k, etc. When you have a very specific question such as some of the ones you posed here, I have found better results on forums such as those. This forum has some very capable people, but relatively few regular posters. SQL Server is such a broad product that by now it takes a number of people specialized in different aspects of it to solve many of the harder problems. Most of those specialists are solving problems that the wizards in sql server cannot begin to address. Good luck. David ------------------------------ Message: 6 Date: Wed, 2 May 2007 07:55:50 -0400 From: "JWColby" <jwcolby at colbyconsulting.com> Subject: Re: [dba-SQLServer] Bulk insert To: <dba-sqlserver at databaseadvisors.com> Message-ID: <002e01c78cb0$d6e93950$657aa8c0 at m6805> Content-Type: text/plain; charset="us-ascii" Arthur knock it off. I haven't even begun to explore what SQL Server in general can do. I asked a whole STREAM of questions about using SSIS to do this and you and everyone else were strangely silent. This list is exactly about getting HELP not "your statements are preposterous". If you can't answer how to do it, that is fine (notice that you STILL aren't offering an answer) but if YOU DON'T KNOW (being the kung fu master of SQL Server) then exactly how am I supposed to figure it out. Preposterous my statements may be (though you aren't showing me proof of that) but insulting your statements are, and not helpful to boot. I came up with a solution to my problem that involved a TOY. YOU OTOH do NOT offer a solution but hint that someday when I too am a kung fu master I will be able to solve my problems masterfully. Which I do not doubt. I respectfully suggest that you put your money where your mouth is. John W. Colby Colby Consulting www.ColbyConsulting.com -----Original Message----- From: dba-sqlserver-bounces at databaseadvisors.com [mailto:dba-sqlserver-bounces at databaseadvisors.com] On Behalf Of Arthur Fuller Sent: Tuesday, May 01, 2007 11:33 PM To: dba-sqlserver at databaseadvisors.com Subject: Re: [dba-SQLServer] Bulk insert To put it as gently as possible, you haven't even begun to explore what SSIS can do. Several of your statements are so preposterous as to lie beneath rebuttal. I suggest that when you have a spare weekend, you investigate the SSIS documentation. There you will find abundant insight into how to handle CSV and fixed-width files, not to mention a whole lot more. I'm sorry that the wizards couldn't get you from here to there, but just because you couldn't figure out immediately how to do it does NOT mean it's the tool's problem. SSIS is a quantum leap beyond what DTS could do, and even it could handle your CSV and trailing spaces problems without difficulty. I respectfully suggest it's time for input (read some documentation) not output. This is not to say that SSIS is problem-free, but the trivial issues you raise are solvable in a few minutes of reading. Arthur _______________________________________________ dba-SQLServer mailing list dba-SQLServer at databaseadvisors.com http://databaseadvisors.com/mailman/listinfo/dba-sqlserver http://www.databaseadvisors.com