Control-M vs SQL Server Agent

Hi
We have a plan to migrate from SQL Server Agent to Control for job schedulin
g.
For those who have done this or attempted to it, I would be very grateful if
you could share some of your experience.
I would be interested in:
- Which scripting language did you use for wrapper scripts?
- Did you continue using maintenance plans for backups, dbcc's, re-indixing,
etc.?
- How did you run dts packages from control-M and were you able to report
useful message through control-M?
- Why would you, or would you not, migrate to control-M
Many thanks,Hi
We are at a start of a 300 SQL Server 2000 migration project to Control-M.
It is the corporate standard, so we don't have much choice.
We will probably use PERL for the wrappers, but VBS might still be used.
Everything will be migrated, but we have a toolset of PERL scripts that does
backups, restores, cold loads etc. This will help a lot.
The DTS stuff, well, it will be moved, but I don't think we will get good
error reporting out of it, unless each DTS package logs what it is doing.
In 60 days, we have to be finished.....
Regards
Mike
"dave222" wrote:

> Hi
> We have a plan to migrate from SQL Server Agent to Control for job schedul
ing.
> For those who have done this or attempted to it, I would be very grateful
if
> you could share some of your experience.
> I would be interested in:
> - Which scripting language did you use for wrapper scripts?
> - Did you continue using maintenance plans for backups, dbcc's, re-indixin
g,
> etc.?
> - How did you run dts packages from control-M and were you able to report
> useful message through control-M?
> - Why would you, or would you not, migrate to control-M
> Many thanks,

Control-M vs SQL Server Agent

Hi
We have a plan to migrate from SQL Server Agent to Control for job scheduling.
For those who have done this or attempted to it, I would be very grateful if
you could share some of your experience.
I would be interested in:
- Which scripting language did you use for wrapper scripts?
- Did you continue using maintenance plans for backups, dbcc's, re-indixing,
etc.?
- How did you run dts packages from control-M and were you able to report
useful message through control-M?
- Why would you, or would you not, migrate to control-M
Many thanks,Hi
We are at a start of a 300 SQL Server 2000 migration project to Control-M.
It is the corporate standard, so we don't have much choice.
We will probably use Perl for the wrappers, but VBS might still be used.
Everything will be migrated, but we have a toolset of Perl scripts that does
backups, restores, cold loads etc. This will help a lot.
The DTS stuff, well, it will be moved, but I don't think we will get good
error reporting out of it, unless each DTS package logs what it is doing.
In 60 days, we have to be finished.....
Regards
Mike
"dave222" wrote:
> Hi
> We have a plan to migrate from SQL Server Agent to Control for job scheduling.
> For those who have done this or attempted to it, I would be very grateful if
> you could share some of your experience.
> I would be interested in:
> - Which scripting language did you use for wrapper scripts?
> - Did you continue using maintenance plans for backups, dbcc's, re-indixing,
> etc.?
> - How did you run dts packages from control-M and were you able to report
> useful message through control-M?
> - Why would you, or would you not, migrate to control-M
> Many thanks,

Control-M vs SQL Server Agent

Hi
We have a plan to migrate from SQL Server Agent to Control for job scheduling.
For those who have done this or attempted to it, I would be very grateful if
you could share some of your experience.
I would be interested in:
- Which scripting language did you use for wrapper scripts?
- Did you continue using maintenance plans for backups, dbcc's, re-indixing,
etc.?
- How did you run dts packages from control-M and were you able to report
useful message through control-M?
- Why would you, or would you not, migrate to control-M
Many thanks,
Hi
We are at a start of a 300 SQL Server 2000 migration project to Control-M.
It is the corporate standard, so we don't have much choice.
We will probably use Perl for the wrappers, but VBS might still be used.
Everything will be migrated, but we have a toolset of Perl scripts that does
backups, restores, cold loads etc. This will help a lot.
The DTS stuff, well, it will be moved, but I don't think we will get good
error reporting out of it, unless each DTS package logs what it is doing.
In 60 days, we have to be finished.....
Regards
Mike
"dave222" wrote:

> Hi
> We have a plan to migrate from SQL Server Agent to Control for job scheduling.
> For those who have done this or attempted to it, I would be very grateful if
> you could share some of your experience.
> I would be interested in:
> - Which scripting language did you use for wrapper scripts?
> - Did you continue using maintenance plans for backups, dbcc's, re-indixing,
> etc.?
> - How did you run dts packages from control-M and were you able to report
> useful message through control-M?
> - Why would you, or would you not, migrate to control-M
> Many thanks,

Container content edit wierdness

I attempted to move some tasks into a new sequence container. It failed saying element cannot be found in a collection. Now I find that visually the tasks do not appear in the container. But in some ways they are. I can not try to move the tasks to the container, or I get the same "element can not be found". If I execute the container, the tasks outside the container run.

I thought to CUT and PASTE my tasks, but then it says "The package contains one or more event handlers for this task. Deleting the task will also delete the event handlers and the event handler context."Good luck with this one. I hope others have found a solution, or perhaps SP2 fixes it. Which version of SSIS are you using? I have the same problem and fight with that all of the time.

(Sorry, I know that's not what you wanted to hear.)|||

Closing and reopening BIDS usually fixes it for me!!

-Jamie

|||Opening and closing BIDS did not help me.

I took a chance, and ignored the cut/paste failure. I am back in business now.|||Yet another problem is SP2 update fails for me. Hoping this might fix it, but I was forced to look for a work around instead.

Thanks for sharing your experience.