Cann't create Legacy (SQL 2000) Maintenance Plans

I recently installed the SQL Server 2005 Management Studio on my workstation
and the install of this new tool removed the old SQL Server 2000 Enterprise
Manager.
Since 99% of my installed server base is still SQL Server 2000, here’s my
question.
How am I supposed to manage my SQL Server 2000 instances with the SQL Server
2005 tools?
When I connect to a SQL Server 2000 instance, using SQL 2005 Management
Studio, I can see under Legacy -> Database Maintenance Plans, the existing
plans; however I cannot create any new Legacy Maintenance plans.
Kurt
It sounds bad but you should have thought of that before you upgraded then.
The documentation in 2005 clearly spells this out. If you need to change or
create new 2000 maintenance plans then you should have a machine with 2000
EM on it for that purpose. You must have chosen to upgrade your existing
instance instead of doing a side by side installation. There is no problem
running 2000 and 2005 on the same box and having both EM and SSMS running at
the same time. You can reinstall 2000 client tools but I am not sure if you
need to uninstall 2005 first or not. I would try it first and see.
Andrew J. Kelly SQL MVP
Solid Quality Mentors
"kmoskal@.newsgroups.nospam" <zork@.newsgroups.nospam> wrote in message
news:1FC128B9-88F0-42CA-8684-1445A06BA3B0@.microsoft.com...
>I recently installed the SQL Server 2005 Management Studio on my
>workstation
> and the install of this new tool removed the old SQL Server 2000
> Enterprise
> Manager.
> Since 99% of my installed server base is still SQL Server 2000, here’s my
> question.
> How am I supposed to manage my SQL Server 2000 instances with the SQL
> Server
> 2005 tools?
> When I connect to a SQL Server 2000 instance, using SQL 2005 Management
> Studio, I can see under Legacy -> Database Maintenance Plans, the existing
> plans; however I cannot create any new Legacy Maintenance plans.
>
>
>
> --
> Kurt

Cannot save maintenance plans

I am running SQL 2005 standard SP2 and I cannot save maintenance plans. Using the wizard I create the plan but it always fails with the following error messages:

An exception occurred while executing a Transact_SQL statement or batch

Invalid column name 'from_msx'.

Invalid column name 'has_targets'. (Microsoft SQL Server , Error: 207)

Invalid column name 'msx_job_id'. (Microsoft SQL Server, Error: 207)

Thanks

Todd

The column names you mention were added in SP2. This indicates that there is a mix of SP2 and earlier functionality involved in this problem.

Bring all elements up to SP2. If you have done so already, inspect installler logs to see if sp2 setup ran without error.

Good luck,

jkh