Hi,

I am very new to DTS, so hope my quesion is not silly.

We are working on a long-term project (C#, about 50 men years,
scheduled to 3/2005). We are based on SQL server 2000.( although our
deployment dates will probably coincide with Yukon release, sigh )

Part of the project is integrating data from about 15 other systems on
a daily basis. Data is sent to us in text files, and integrated into
the SQL server using DTS and lots of .Net application code. (It is
"Data to application" situation, and not exactly ETL)

Question: We were thinking of using Yukon as our DTS platform, to do
our ETL type processing into the SQL 2000 server. This could earn us
the following benefits:

1) Better integration to .Net development
2) Saving migration pain when we eventually migrate to Yukon.
3) Better DTS.

Is it technically possible to do DTS on Yukon into SQL 2000 ?
Is the "Better DTS" of Yukon really worth the hassle?

Thanks!

Tzahi

Oh yes. Yukon DTS is a better animal than v2000 DTS IMHO. Microsoft have
made huge improvements in the code and types of things being able to be
implemented in Yukon versus v2000.

It sounds as though currently you are using .Net code as "Glue" code. i.e.
you cannot do what you want natively in DTS so have to tack something on the
side to make it fit. If this is the case then yes Yukon DTS will be a
Godsend to you. It is though a whole different paradigm. You can almost
forget what you know in v2000 and have to start anew in Yukon. Don't let
that put you off though, it is truly a better product.

Go to the MS site and try to get yourself on the Public Beta program.

--
--

Allan Mitchell MCSE,MCDBA, (Microsoft SQL Server MVP)
www.SQLDTS.com - The site for all your DTS needs.
I support PASS - the definitive, global community
for SQL Server professionals - http://www.sqlpass.org


"Tzahi" <tzahij (AT) hotmail (DOT) com> wrote

Hi Allen,

Thanks a lot for your answer, and you have certainly convinced me (
well, isn't too hard convincing a techi to use the newest and
greatest :-) ) – but my managers being what they are (smart managers)
will probably ask the following questions:

1) we are basically using Yukon purely as an ETL engin, similar to
Informatica. Is it reasonable? Isn't Informatica a much better tool ?
2) Are there things I could do with DTS v2000 that is part of my DB
that I can't do with Yukon DTS running on another machine.
3) Is it possible to debug .Net code that is acticated by Yukon DTS

And thanks again for you help

Tzahi

I have never used Informatica but I do know MS have put a lot of time and
energy into Yukon DTS. Theu want it to be the best.
Everything you do in 2000 you can do with Yukon and then some.
You can use Breakpoints in Yukon DTS



--
--

Allan Mitchell MCSE,MCDBA, (Microsoft SQL Server MVP)
www.SQLDTS.com - The site for all your DTS needs.
I support PASS - the definitive, global community
for SQL Server professionals - http://www.sqlpass.org


"Tzahi" <tzahij (AT) hotmail (DOT) com> wrote

I agree, Yukon is far better, but "It is though a whole different
paradigm". Specifics below-

In message <662cede5.0404101137.4e74cab1 (AT) posting (DOT) google.com>, Tzahi
<tzahij (AT) hotmail (DOT) com> writes
more features, but horrible to use. Now with Yukon DTS, that gap has
closed on the feature side, if not disappeared. It really is an
enterprise capable ETL platform now.

do it may be very different through, but this will be for the better.

wrote code for in SQL2K are no longer necessary. If you do want custom
tasks or transformation components, then this can still be done, and I
think it is much easier and more powerful.

You may want to wait a while for Beta 2 to be available though.

--
Darren Green (SQL Server MVP)
DTS - http://www.sqldts.com

PASS - the definitive, global community for SQL Server professionals
http://www.sqlpass.org

We use both informatica and DTS (SQL2000) in our environment. Informatica
was orginally selected because we were using a Lotus Notes source and the
people making the decision on what tool to use did not have confidence in
DTS. My experience is that anything you can do in Informatica you can do in
DTS. The main advantage to Informatica it ability to connect to mainframe
and other legacy systems. Informatica does a great job at connecting and
moving data from just about any system you can throw at it. If your sources
are only Microsoft products then Informatica will be overkill. You also
don't have to do any scripting with Informatica which is an advantage to
non-scripts. The main disadvantages to Informatica, from my prospective, is
that very few shop use it with SQL Server. I would guess less than 2%. The
support for SQL Server customers has been terrible from my experience. It
took 8 months to get a patch that worked for a bug that took 4 months for me
to convince there support staff was in fact a bug. To there defense, they
fired the support manager I was working with.

Kyle

"Tzahi" <tzahij (AT) hotmail (DOT) com> wrote

In message <CXHgc.497366$Po1.349289 (AT) twister (DOT) tampabay.rr.com>, kyle burke
<theburkes97 (AT) hotmail (DOT) com> writes
Kyle,

If you dislike scripts and glue code, which is so prevalent in flexible
packages today, then you may want to take a look at Yukon DTS as there
are a lot less reasons to use it, and 90% of the times you can, you
probably shouldn't, but bad habits are hard to break

Darren

--
Darren Green (SQL Server MVP)
DTS - http://www.sqldts.com

PASS - the definitive, global community for SQL Server professionals
http://www.sqlpass.org