Re: SQL 2005, DTS, problems, problems, problems, etc..

Tech Tip: Click here to run a free scan for Windows Errors and optimize PC performance

Hello Roz,

Yep I'm here. Left me a post where. If you sent me a mail personally it may have been cleaned up by my mail filter system



Allan Mitchell
www.SQLDTS.com
www.SQLIS.com
www.Konesans.com

Allan,

You there. Left you a post yesterday.

Thanks

Roz

"Allan Mitchell" wrote:

Hello Allan,

Sorry just so I am clear. MSDB stored packages are still MSDB
(sysdtspackages90) the file store stores them to a special folder.
You can see more if you have a look at this file MsDtsSrvr.ini in
..\Microsoft SQL Server\90\DTS\Packages

Allan Mitchell
www.SQLDTS.com
www.SQLIS.com
www.Konesans.com
Hello Roz,

In Management studio | Object Explorer hit the Connect button

Connect to Integration Services

You will find your packages here.

No they are not still in a project. These packages are the
packages. How would it look if you used DTUtil to move them to
A.N.Other server that could not see the original Project? They
would still work.

Have a look at DTUtil in BOL and here

ms-help://MS.SQLCC.v9/MS.SQLSVR.v9.en/extran9/html/ef18ec11-b536-47d
9- abd1-794099f43486.htm

Allan Mitchell
www.SQLDTS.com
www.SQLIS.com
www.Konesans.com
Allan,

Got a quick question. I've followed your advice, and am now
calling my SQL 2000 packages via the "Execute 2000 package task" in
a 2005 package. Once I've saved the package to my MSDB, I go into
Mgt Studio, connect to IS, and correctly see the package in my MSDB
store. My question is, how can I access the actual package from
Mgt. Studio (if possible)?, and how do I know where the true
location of the actual package is from within Mgt. Studio. Seems
to me in Mgt Studio/IS, the MSDB store simply shows "pointers" of
the names of the packages, but these aren't the real packages. The
real packages are part of an Integration Services project, and it
is there I must look to see the actual package. Mgt.Studio/IS
doesn't really show me where the package's acutal "source package"
is.

Hope I don't sound confusing...

Thanks Roz

"Allan Mitchell" wrote:

Hello Roz,

The only thing i can initially think of is that 2K massaged datat
between types. 2K5 is not so forgiving. Could this be it?

Allan Mitchell
www.SQLDTS.com
www.SQLIS.com
www.Konesans.com
Allan,

I appreciate your comments, and suggestions. However, in my
case, using the "Execute 2000 package task" isn't an option
because I've migrated my 2000 databases to 2005, so that is why I
need to open/edit the packages to point them to the new datbase.
Like I said in a previous post last week, redoing some of these
packages from scratch will take some time. Eventually, we will
have to redo from scratch, because as I mentioned last week,
"migrating" to SQL 20005 IS, drops all columns mappings, and some
of my tables have 50+ columns.

I still can't understand how a simple column mapping gets dropped
during a migration.

Thanks again Allan,

Roz

"Allan Mitchell" wrote:

Hello Roz,

In defence of the Legacy framework I am not having the same
problems
as yourself. That does not mean though that it is not painful
for
you. Personally I will not be opening too many 2K packages in
2K5.
I will be using the Execute 2000 Package task and leaving it at
that.
I will also not be doing too many upgrades, I will redo them
from
scratch do I can ensure best practices and therefore quality in
the
2K5 version of the package.
Allan Mitchell
www.SQLDTS.com
www.SQLIS.com
www.Konesans.com
Is anyone else out there having problems with SQL 2005
opening/editing/saving SQL 2000 DTS packages...even with the
Backward compatibility/2000 DTS Components installed?
Specifically, after installing these two downloads, I can Open
a DTS 2000 package, but when opened, the icons/graphics are
displayed crazily. Even after "cleaning up" (ie remapping
columns, editing source/destination connections); when I try to
save the newly edited package, I get a "The DTS host failed to
open or save the package properly" error message.

The benefit of continuing to use DTS 2000 packages in SQL 2005
is
greatly appreciated, but I'm not too certain all the bugs were
addressed and resolved. Microsoft, if you're listening, please
respond with a "solid" solution on how to get this resolved.
I've
bent over backwards trying to sell my company on this upgrade,
but
so far we've encountered nothing but roadblocks, and I've got
major
eggs on my face. With the great help of Allan Mitchell; I've
been
able to navigate the rough edges, but it shouldn't be this way.
Just to add, my staff and I are very versed in SQL Server, are
certified MCDBAs; and aren't just venting misguided
frustrations
here. Our problems/issues are valid and legitimate, so I'd
strongly
appreciate some help.
Hopeless and Semi-Helpless in San Antonio,
Roz


.

Quantcast