Migrating DTS packages from SQL2000 to SQL2005

Hi,
My initial tests show that this feature will only see DTS Local Packages.
How can we migrate the DTS Meta Data Services Packages?
Thanks
Chris
The requirements for migrating DTS packages saved to the
repository are explained in Books Online help topic:
Using the Package Migration Wizard
http://msdn2.microsoft.com/en-us/library/ms143496.aspx
-Sue
On Tue, 19 Sep 2006 08:04:56 -0600, "Chris Wood"
<anonymous@.discussions.microsoft.com> wrote:

>Hi,
>My initial tests show that this feature will only see DTS Local Packages.
>How can we migrate the DTS Meta Data Services Packages?
>Thanks
>Chris
>
|||Sue,
This mentions Repository packages only if SQL2000, SQL2000 tools or the
Repository files are present on the local computer, the server that the
Migration Wizard is being run on I assume? As we have msdb as our Repository
we would have to migrate the SQL2000 msdb to the SQL2005 to find the Meta
Data Services packages?
Thanks
Chris
"Sue Hoegemeier" <Sue_H@.nomail.please> wrote in message
news:7a20h2pq7uggrgp7iuvggghvdpu343mms8@.4ax.com...
> The requirements for migrating DTS packages saved to the
> repository are explained in Books Online help topic:
> Using the Package Migration Wizard
> http://msdn2.microsoft.com/en-us/library/ms143496.aspx
> -Sue
> On Tue, 19 Sep 2006 08:04:56 -0600, "Chris Wood"
> <anonymous@.discussions.microsoft.com> wrote:
>
|||Yes...on the server where the migration wizard is being run.
The wizard needs the repository files to read the packages.
You just need the repository redistributable files on that
server.
-Sue
On Tue, 19 Sep 2006 10:07:43 -0600, "Chris Wood"
<anonymous@.discussions.microsoft.com> wrote:

>Sue,
>This mentions Repository packages only if SQL2000, SQL2000 tools or the
>Repository files are present on the local computer, the server that the
>Migration Wizard is being run on I assume? As we have msdb as our Repository
>we would have to migrate the SQL2000 msdb to the SQL2005 to find the Meta
>Data Services packages?
>Thanks
>Chris
>"Sue Hoegemeier" <Sue_H@.nomail.please> wrote in message
>news:7a20h2pq7uggrgp7iuvggghvdpu343mms8@.4ax.com.. .
>
|||Thanks Sue.
The analysts changed the packages to Local packages so we could use the
Migration Wizard.
Now we have migrated them we had to install the SQL2000 DTS Designer
Components, from the Feature Pack, but we still cannot see the migrated
packages. I remember an article by Brian Moran in SQL Mag on how to fix this
problem but I don't have the article on hand.
Can someone tell me the fix please? I think it had to do with the registry.
Thanks
Chris
"Sue Hoegemeier" <Sue_H@.nomail.please> wrote in message
news:2t81h2trkbmjlfsve86v8egsgs9lc01cci@.4ax.com...
> Yes...on the server where the migration wizard is being run.
> The wizard needs the repository files to read the packages.
> You just need the repository redistributable files on that
> server.
> -Sue
> On Tue, 19 Sep 2006 10:07:43 -0600, "Chris Wood"
> <anonymous@.discussions.microsoft.com> wrote:
>

Migrating DTS packages from SQL2000 to SQL2005

Hi,
My initial tests show that this feature will only see DTS Local Packages.
How can we migrate the DTS Meta Data Services Packages?
Thanks
ChrisThe requirements for migrating DTS packages saved to the
repository are explained in Books Online help topic:
Using the Package Migration Wizard
http://msdn2.microsoft.com/en-us/library/ms143496.aspx
-Sue
On Tue, 19 Sep 2006 08:04:56 -0600, "Chris Wood"
<anonymous@.discussions.microsoft.com> wrote:
>Hi,
>My initial tests show that this feature will only see DTS Local Packages.
>How can we migrate the DTS Meta Data Services Packages?
>Thanks
>Chris
>|||Sue,
This mentions Repository packages only if SQL2000, SQL2000 tools or the
Repository files are present on the local computer, the server that the
Migration Wizard is being run on I assume? As we have msdb as our Repository
we would have to migrate the SQL2000 msdb to the SQL2005 to find the Meta
Data Services packages?
Thanks
Chris
"Sue Hoegemeier" <Sue_H@.nomail.please> wrote in message
news:7a20h2pq7uggrgp7iuvggghvdpu343mms8@.4ax.com...
> The requirements for migrating DTS packages saved to the
> repository are explained in Books Online help topic:
> Using the Package Migration Wizard
> http://msdn2.microsoft.com/en-us/library/ms143496.aspx
> -Sue
> On Tue, 19 Sep 2006 08:04:56 -0600, "Chris Wood"
> <anonymous@.discussions.microsoft.com> wrote:
>>Hi,
>>My initial tests show that this feature will only see DTS Local Packages.
>>How can we migrate the DTS Meta Data Services Packages?
>>Thanks
>>Chris
>|||Yes...on the server where the migration wizard is being run.
The wizard needs the repository files to read the packages.
You just need the repository redistributable files on that
server.
-Sue
On Tue, 19 Sep 2006 10:07:43 -0600, "Chris Wood"
<anonymous@.discussions.microsoft.com> wrote:
>Sue,
>This mentions Repository packages only if SQL2000, SQL2000 tools or the
>Repository files are present on the local computer, the server that the
>Migration Wizard is being run on I assume? As we have msdb as our Repository
>we would have to migrate the SQL2000 msdb to the SQL2005 to find the Meta
>Data Services packages?
>Thanks
>Chris
>"Sue Hoegemeier" <Sue_H@.nomail.please> wrote in message
>news:7a20h2pq7uggrgp7iuvggghvdpu343mms8@.4ax.com...
>> The requirements for migrating DTS packages saved to the
>> repository are explained in Books Online help topic:
>> Using the Package Migration Wizard
>> http://msdn2.microsoft.com/en-us/library/ms143496.aspx
>> -Sue
>> On Tue, 19 Sep 2006 08:04:56 -0600, "Chris Wood"
>> <anonymous@.discussions.microsoft.com> wrote:
>>Hi,
>>My initial tests show that this feature will only see DTS Local Packages.
>>How can we migrate the DTS Meta Data Services Packages?
>>Thanks
>>Chris
>>
>|||Thanks Sue.
The analysts changed the packages to Local packages so we could use the
Migration Wizard.
Now we have migrated them we had to install the SQL2000 DTS Designer
Components, from the Feature Pack, but we still cannot see the migrated
packages. I remember an article by Brian Moran in SQL Mag on how to fix this
problem but I don't have the article on hand.
Can someone tell me the fix please? I think it had to do with the registry.
Thanks
Chris
"Sue Hoegemeier" <Sue_H@.nomail.please> wrote in message
news:2t81h2trkbmjlfsve86v8egsgs9lc01cci@.4ax.com...
> Yes...on the server where the migration wizard is being run.
> The wizard needs the repository files to read the packages.
> You just need the repository redistributable files on that
> server.
> -Sue
> On Tue, 19 Sep 2006 10:07:43 -0600, "Chris Wood"
> <anonymous@.discussions.microsoft.com> wrote:
>>Sue,
>>This mentions Repository packages only if SQL2000, SQL2000 tools or the
>>Repository files are present on the local computer, the server that the
>>Migration Wizard is being run on I assume? As we have msdb as our
>>Repository
>>we would have to migrate the SQL2000 msdb to the SQL2005 to find the Meta
>>Data Services packages?
>>Thanks
>>Chris
>>"Sue Hoegemeier" <Sue_H@.nomail.please> wrote in message
>>news:7a20h2pq7uggrgp7iuvggghvdpu343mms8@.4ax.com...
>> The requirements for migrating DTS packages saved to the
>> repository are explained in Books Online help topic:
>> Using the Package Migration Wizard
>> http://msdn2.microsoft.com/en-us/library/ms143496.aspx
>> -Sue
>> On Tue, 19 Sep 2006 08:04:56 -0600, "Chris Wood"
>> <anonymous@.discussions.microsoft.com> wrote:
>>Hi,
>>My initial tests show that this feature will only see DTS Local
>>Packages.
>>How can we migrate the DTS Meta Data Services Packages?
>>Thanks
>>Chris
>>
>

Migrating DTS packages from SQL2000 to SQL2005

Hi,
My initial tests show that this feature will only see DTS Local Packages.
How can we migrate the DTS Meta Data Services Packages?
Thanks
ChrisThe requirements for migrating DTS packages saved to the
repository are explained in Books Online help topic:
Using the Package Migration Wizard
http://msdn2.microsoft.com/en-us/library/ms143496.aspx
-Sue
On Tue, 19 Sep 2006 08:04:56 -0600, "Chris Wood"
<anonymous@.discussions.microsoft.com> wrote:

>Hi,
>My initial tests show that this feature will only see DTS Local Packages.
>How can we migrate the DTS Meta Data Services Packages?
>Thanks
>Chris
>|||Sue,
This mentions Repository packages only if SQL2000, SQL2000 tools or the
Repository files are present on the local computer, the server that the
Migration Wizard is being run on I assume? As we have msdb as our Repository
we would have to migrate the SQL2000 msdb to the SQL2005 to find the Meta
Data Services packages?
Thanks
Chris
"Sue Hoegemeier" <Sue_H@.nomail.please> wrote in message
news:7a20h2pq7uggrgp7iuvggghvdpu343mms8@.
4ax.com...
> The requirements for migrating DTS packages saved to the
> repository are explained in Books Online help topic:
> Using the Package Migration Wizard
> http://msdn2.microsoft.com/en-us/library/ms143496.aspx
> -Sue
> On Tue, 19 Sep 2006 08:04:56 -0600, "Chris Wood"
> <anonymous@.discussions.microsoft.com> wrote:
>
>|||Yes...on the server where the migration wizard is being run.
The wizard needs the repository files to read the packages.
You just need the repository redistributable files on that
server.
-Sue
On Tue, 19 Sep 2006 10:07:43 -0600, "Chris Wood"
<anonymous@.discussions.microsoft.com> wrote:

>Sue,
>This mentions Repository packages only if SQL2000, SQL2000 tools or the
>Repository files are present on the local computer, the server that the
>Migration Wizard is being run on I assume? As we have msdb as our Repositor
y
>we would have to migrate the SQL2000 msdb to the SQL2005 to find the Meta
>Data Services packages?
>Thanks
>Chris
>"Sue Hoegemeier" <Sue_H@.nomail.please> wrote in message
> news:7a20h2pq7uggrgp7iuvggghvdpu343mms8@.
4ax.com...
>|||Thanks Sue.
The analysts changed the packages to Local packages so we could use the
Migration Wizard.
Now we have migrated them we had to install the SQL2000 DTS Designer
Components, from the Feature Pack, but we still cannot see the migrated
packages. I remember an article by Brian Moran in SQL Mag on how to fix this
problem but I don't have the article on hand.
Can someone tell me the fix please? I think it had to do with the registry.
Thanks
Chris
"Sue Hoegemeier" <Sue_H@.nomail.please> wrote in message
news:2t81h2trkbmjlfsve86v8egsgs9lc01cci@.
4ax.com...
> Yes...on the server where the migration wizard is being run.
> The wizard needs the repository files to read the packages.
> You just need the repository redistributable files on that
> server.
> -Sue
> On Tue, 19 Sep 2006 10:07:43 -0600, "Chris Wood"
> <anonymous@.discussions.microsoft.com> wrote:
>
>sql

Migrate MSDE data to SQL 2000

I have local copy of MSDE 2000 on an XP workstation.
My program has already been reconfigured to point to a remote (from the XP
viewpoint) SQL 2000 server. As such, it has created the 2 databases that it
uses and is already populating those databases with data.
The question is, how do I get the "old" data from MSDE on the XP box into
the "new" databases on the remote SQL server?
When I try to use DTS and choosing the default of OLE Provider for SQL for
the source, I can't connect to the XP MSDE, which is using SQL Auth. I know
I am using the correct "sa" password for the MSDE database.
Robert
You have a few options: DTS, Detatch/Reattach, or Backup/Restore.
I prefer to backup on the old server, copy the backup file to the new
server, and restore it on the new server. This is fairly easy to do. Just
make sure you create the users from the old server on the new server first,
and then run sp_change_users_login to eliminate orphaned users after you do
the restore.
"Robert Gandrud" wrote:

> I have local copy of MSDE 2000 on an XP workstation.
> My program has already been reconfigured to point to a remote (from the XP
> viewpoint) SQL 2000 server. As such, it has created the 2 databases that it
> uses and is already populating those databases with data.
> The question is, how do I get the "old" data from MSDE on the XP box into
> the "new" databases on the remote SQL server?
> When I try to use DTS and choosing the default of OLE Provider for SQL for
> the source, I can't connect to the XP MSDE, which is using SQL Auth. I know
> I am using the correct "sa" password for the MSDE database.
> Robert
|||As far as I know, the only user is the "sa" user in the old MSDE database.
What then?
"Dan" wrote:
[vbcol=seagreen]
> You have a few options: DTS, Detatch/Reattach, or Backup/Restore.
> I prefer to backup on the old server, copy the backup file to the new
> server, and restore it on the new server. This is fairly easy to do. Just
> make sure you create the users from the old server on the new server first,
> and then run sp_change_users_login to eliminate orphaned users after you do
> the restore.
> "Robert Gandrud" wrote:
|||hi Robert,
Robert Gandrud wrote:
> I have local copy of MSDE 2000 on an XP workstation.
> My program has already been reconfigured to point to a remote (from
> the XP viewpoint) SQL 2000 server. As such, it has created the 2
> databases that it uses and is already populating those databases with
> data.
> The question is, how do I get the "old" data from MSDE on the XP box
> into the "new" databases on the remote SQL server?
> When I try to use DTS and choosing the default of OLE Provider for
> SQL for the source, I can't connect to the XP MSDE, which is using
> SQL Auth. I know I am using the correct "sa" password for the MSDE
> database.
>
MSDE installs by default disabling network protocols...in order to them
after installation you have to run the
Server Network Utility (svrnetcn.exe) and enabling the desired
protocol(s)...
Win XP Windows Firewall could be an issue too and please have a look at
http://support.microsoft.com/kb/841251/en-us in order to enable remote
connectivity...
Andrea Montanari (Microsoft MVP - SQL Server)
http://www.asql.biz/DbaMgr.shtmhttp://italy.mvps.org
DbaMgr2k ver 0.16.0 - DbaMgr ver 0.61.0
(my vb6+sql-dmo little try to provide MS MSDE 1.0 and MSDE 2000 a visual
interface)
-- remove DMO to reply
sql

migrate a local SQL user account

whats the simplest way to migrate a user account from a master development SQL server to local development sql servers and also to a production server?

we can recreate the SQL account everywhere, but if we take a backup from one machine and restore to another, we loose access because the accounts arent truly the same account.Very few info can be found in sql books online.
You need to read Microsoft Knowledge Base Article - 246133
check out this link
http://support.microsoft.com/default.aspx?scid=kb;[LN];Q246133|||thanks for the article...i need to run the process that keeps the SID intact.

somehow i new the was no copy/paste solution... :-(