Migration SQL server 2000 to 2005, with heavy use of DTS

We have a big migration from SQL server 2000 to 2005
It is a big procedure aith millions of records and it uses DTSs
heavily, so I am asking some hints on s your experience on
1. "basic" migration of DB ib itself
2. DTS: we read that the Dynamic Properties used by DTS are NOT fully
supported and that would be a great problem for us
Any reporting of other known issues - small, medium or big -
will be greatly appreciated.
Thank you so muchSeveral things to do, the ones I remember:
1) Check BOL section 'Upgrading to SQL Server 2005', 'Backward
Compatibility'. Look for deprecated and discontinued features, breaking
changes and behavior changes.
2) Use the SQL Server Upgrade Advisor and follow its recommendations
3) You may want to consider moving the DTS packages without converting to
SSIS. Check also 'Upgrading to SQL Server 2005', 'Backward Compatibility' fo
r
DTS.
4) Test everything.
Hope this helps,
Ben Nevarez
Senior Database Administrator
AIG SunAmerica
"baruffa66@.gmail.com" wrote:

> We have a big migration from SQL server 2000 to 2005
> It is a big procedure aith millions of records and it uses DTSs
> heavily, so I am asking some hints on s your experience on
> 1. "basic" migration of DB ib itself
> 2. DTS: we read that the Dynamic Properties used by DTS are NOT fully
> supported and that would be a great problem for us
> Any reporting of other known issues - small, medium or big -
> will be greatly appreciated.
> Thank you so much
>|||Hi,
First, if you have not yet done so, get the "Microsoft SQL Server 2005
Upgrade Advisor". You can run this against your SQL Server 2000 server and
it will produce a report on problem areas that you may need to fix. We did
not have much problem, but the old style outer joins (*=, =*) are
deprecated. Also, if you have code that uses system tables some of those
have changed or vanished.
Passwords on 2005 are case-sensitive. This will cause you some problems if
you have code registered to login with a password in a different case from
that stored on the server. (SQL Server 2000 would forgive that, 2005 will
not.)
Since you are DTS heavy, there are "Microsoft SQL Server 2005 Backward
Compatibility Components" and the "Microsoft SQL Server 2000 DTS Designer
Components" to run on SQL Server 2005. Of course, it is the course of
wisdom to upgrade your packages to SSIS prior to SQL Server 2008, but this
can get you into SQL Server 2005 faster, and let you catch up on your DTS
packages one at a time, rather than all at once.
http://technet.microsoft.com/en-us/...aspx#designtime
These additional packages can be found at Feature Pack for Microsoft SQL
Server 2005 - February 2007
a42ec403d17&displaylang=en" target="_blank">http://www.microsoft.com/downloads/...&displaylang=en
RLF
<baruffa66@.gmail.com> wrote in message
news:b48d3fdf-2700-4855-b220-7bd616f33e40@.n20g2000hsh.googlegroups.com...
> We have a big migration from SQL server 2000 to 2005
> It is a big procedure aith millions of records and it uses DTSs
> heavily, so I am asking some hints on s your experience on
> 1. "basic" migration of DB ib itself
> 2. DTS: we read that the Dynamic Properties used by DTS are NOT fully
> supported and that would be a great problem for us
> Any reporting of other known issues - small, medium or big -
> will be greatly appreciated.
> Thank you so much|||Ben and Russel,
thanks a lot.
We asked 5 professionals,
4 of them have not even indirect experience on this migration,
the fifth says that he didn't migrate but is using a module of 2005
that allows to keep those oldies but goodies DTS
and launch them from 2005, without migrating to the new SSIS.
Ciao