Migration Maint Plns SQL Server 2005 ==> SQL Server 2005

Hello all,

Has anyone been able to migrate a maint plan from one server to another and have it work? I can do the migrition by doing a package export but when I go into the package on the new server and change the connection information I get a guid should contain 32 digits with 4 dashes error message. Does anyone know a work around?

Hi

I'm having the same problem did you ever find a solution for it?

|||I'm having the same problem - and I did not migrate any plan, just created a new one on the new server. I get this error when I try to save/edit the plan.

Toby|||

I have moved this thread to the SQL Server Tools General forum whihc is where Maintenance Plans are best discussed.

Donald Farmer

|||

We have a bug tracking for this this issue and there is no workaround for this issue. I will update more on the status of this bug after following up with my team.

Thanks,

Gops Dwarak

|||

I am experiencing the same problems, have their been any updates on this?

Edward

Migration Maint Plns SQL Server 2005 ==> SQL Server 2005

Hello all,

Has anyone been able to migrate a maint plan from one server to another and have it work? I can do the migrition by doing a package export but when I go into the package on the new server and change the connection information I get a guid should contain 32 digits with 4 dashes error message. Does anyone know a work around?

Hi

I'm having the same problem did you ever find a solution for it?

|||I'm having the same problem - and I did not migrate any plan, just created a new one on the new server. I get this error when I try to save/edit the plan.

Toby|||

I have moved this thread to the SQL Server Tools General forum whihc is where Maintenance Plans are best discussed.

Donald Farmer

|||

We have a bug tracking for this this issue and there is no workaround for this issue. I will update more on the status of this bug after following up with my team.

Thanks,

Gops Dwarak

|||

I am experiencing the same problems, have their been any updates on this?

Edward

Migration Maint Plns SQL Server 2005 ==> SQL Server 2005

Hello all,

Has anyone been able to migrate a maint plan from one server to another and have it work? I can do the migrition by doing a package export but when I go into the package on the new server and change the connection information I get a guid should contain 32 digits with 4 dashes error message. Does anyone know a work around?

Hi

I'm having the same problem did you ever find a solution for it?

|||I'm having the same problem - and I did not migrate any plan, just created a new one on the new server. I get this error when I try to save/edit the plan.

Toby|||

I have moved this thread to the SQL Server Tools General forum whihc is where Maintenance Plans are best discussed.

Donald Farmer

|||

We have a bug tracking for this this issue and there is no workaround for this issue. I will update more on the status of this bug after following up with my team.

Thanks,

Gops Dwarak

|||

I am experiencing the same problems, have their been any updates on this?

Edward

Migration ACCESS --> SQL date field

Hi,
I import an access table with date field in SQL with DTS import/export
wizard.
I got error : data overflow on date field. There is another way to do it ?In the DTS package, transform that column to varchar, and then run isdate()
against the new table to determine which rows need to be repaired.
"Sylvain Provencher" <sylvain.provencher@.nobelia.com> wrote in message
news:uZybbSLpDHA.2268@.TK2MSFTNGP12.phx.gbl...
> Hi,
> I import an access table with date field in SQL with DTS import/export
> wizard.
> I got error : data overflow on date field. There is another way to do it ?
>