Oh the humanity ...

Question

Oh the humanity ...

Viewing 15 posts - 16 through 30 (of 32 total)

You must be logged in to reply to this topic. Login to reply

Juan Sanchez-301264 SSC Enthusiast Points: 101 More actions · Answer 1

Ok Jamie, you're on!

Let me manipulate the data so it hasn't got any kind of personal info in it (it is from one of our customers after all) and I'll send it to ya! If you do it (under 1 min and 17 secs don't forget), I'd love to know how ... no, really I would - I soooo want to be proven wrong on this

Doug B SSC Rookie Points: 30 More actions · Answer 2

I've had the most fun and games trying to use C# and the SSIS object model to program some components and packages to run on the fly SQL statements.

My humble opinion is that I'm going to ask Microsoft to include a complimentary membership in the Hair Club for Men (and Women) with every copy of SQL Server 2005 / SSIS destined for C# developers.

Has anyone had much success programming w/ C# and the object model? I would love to trade notes with you.

Thanks!

DougB

For all responses: There is no implied warranty. Use at your own risk. Kindest Regards,

Doug B

Juan Sanchez-301264 SSC Enthusiast Points: 101 More actions · Answer 3

Sorry Doug, I've only just got into trying to do it through the GUI! Ooh, doing it through C# - hardcore! (And you have my deepest sympathy with the hair thing

david russell-253790 SSCarpal Tunnel Points: 4042 More actions · Answer 4

We scrapped it TOTALLY as part of a major product. Maybe another release... maybe not.

Cheers,

david russell

Doug B SSC Rookie Points: 30 More actions · Answer 5

David ....

Did you scrap SSIS as a whole, or using the SSIS Object Model and C#? If it is the latter, what did you find that was really bad? Maybe I can avoid the same issue.

Thanks!

DB

For all responses: There is no implied warranty. Use at your own risk. Kindest Regards,

Doug B

Juan Sanchez-301264 SSC Enthusiast Points: 101 More actions · Answer 6

Hi David, it would be interesting to hear your experiences of SSIS and why you came to scrap it entirely 🙂

Cheers, Mark

Juan Sanchez-301264 SSC Enthusiast Points: 101 More actions · Answer 7

Well, it appears that no-one has been able to rise to my challenge and convince me that SSIS is an improvement over DTS. Not only is it NOT an improvement, it's one of the most monstrously complicated pieces of poo-poo I have ever seen (apart from trying to program the video to record Coronation Street). I'm afraid the argument of 'it's complicated for a reason' doesn't wash with us - we need the simplicity of DTS. I do feel that Microsoft have missed the point entirely of DTS and have replaced it with something that is just way over the heads of ordinary users.

Of course, all the extra training that is going to be needed for even the most basic of operations means that Bill will be able to afford a new country after all.

Thanks to everyone for contributing.

(Thanks to Jamie for attempting the challenge - did you manage to do it? - you were the only one brave enough to have a go!)

Jamie Thomson SSChampion Points: 11805 More actions · Answer 8

No, I didn't sorry. I promise I still will. Just been very busy y'know!!

-Jamie

Jamie Thomson
http://sqlblog.com/blogs/jamie_thomson

omhoge SSCertifiable Points: 5416 More actions · Answer 9

DTS is gone. So I'm curious what are you doing, writing your ETLs as C#/VB assemblies, doing it all in TSLQ? What's your new methodology?

thanks!

Skål - jh

Bob Clayton Old Hand Points: 392 More actions · Answer 10

I think Microsoft really dropped the ball with SSIS. They took an easy-to-use and very intuitive product, and turned it into a needlessly complex nightmare. Primarily because of the SSIS disaster, we are putting off migrating to SQL 2005 and may even skip this version of SQL Server entirely. We are probably also going to research alternative products.

Our DBAs are also not at all happy with the "visual studio" interface for SQL 2005, but that's a whole other discussion.

Jamie Thomson SSChampion Points: 11805 More actions · Answer 11

Mark,

I finally got around to trying this. I apologise that it took me so long. Everytime I booted up to try it something ended up interrupting me y'know. Emails to answer...IMing etc...

Anyway, I've tried. I spent some time getting famiilar with the import wizard first. Given that I've never used it before I thought that was fair to put me on an equal footing to yourself seeing as you are familiar with DTS2000 import wizard.

Prior to starting the stopwatch I created the table with the CREATE TABLE script that you sent me and placed the source file into c:\temp. Nothing else.

I then used the import wizard to import the data into that table and subsequently save the package to SQL Server. The whole thing took 44 seconds compared to yours, Mark, using DTS which took 77 seconds.

I was also able to rerun the package successfully afterwards - proving that the contents of the table do indeed get deleted (or else it would fail with a PK violation)

I won't crow and proclaim SSIS to be any better on the basis of a simple test like this. I am willing to accept other people's opinions about SSIS being a step backward as long as people accept my own that SSIS is a far superior product than DTS. Remember that one of the motivation for building SSIS and many of the new features was complaints about DTS.

Yes, its a different tool and hence things which worked in DTS won't work the same in SSIS but as with any new tool, get to know how to use it and I'm confident that you will see the benefit.

-Jamie

P.S. Just to prove the test here's the output after running the package from the wizard:

The execution was successful

- Initializing Data Flow Task (Success)

- Initializing Connections (Success)

- Setting SQL Command (Success)

- Setting Source Connection (Success)

- Setting Destination Connection (Success)

- Validating (Warning)

Messages

Warning 0x802092a7: Data Flow Task: Truncation may occur due to inserting data from data flow column "Column 0" with a length of 50 to database column "Branch" with a length of 20.