Deleting jobs when MX Server not available.

Hi All
I have some SQL jobs which I can't delete because they
were originally setup from an MX (master) server. That MX
server is no longer available so how do I delete the jobs?
I assume I'm going to have to delete the entries from the
MSDB datase, but what tables do I need to take the rows
out from?
ThanksIT is easier to just change the originating_server column in sysjobs to your
machine name. This "makes" the jobs normal non-msx jobs. You can do this
with a simple update statement. Note that it is not supported to modify the
system tables directly, so do at your own risk and make sure you have a
backup first.
--
Tibor Karaszi, SQL Server MVP
Archive at:
http://groups.google.com/groups?oi=djq&as_ugroup=microsoft.public.sqlserver
"Jono" <anonymous@.discussions.microsoft.com> wrote in message
news:16c801c3a89e$57848e70$a601280a@.phx.gbl...
> Hi All
> I have some SQL jobs which I can't delete because they
> were originally setup from an MX (master) server. That MX
> server is no longer available so how do I delete the jobs?
> I assume I'm going to have to delete the entries from the
> MSDB datase, but what tables do I need to take the rows
> out from?
> Thanks
>|||Thanks Tibor.
I tried it out and it works like a gem.
Thanks again
-Jono

Deleting inaccessible Sql server jobs

hi all,
we have renamed a server which had sql server on it, all the databases are
still on it and their is no problem accessing them at all, and now after this
the sql server jobs which were on this machine and were running before the
name was changed are crashing everytime they run, when i tried deleted them
since i dont need them any more it pops up and error, i am not even able to
disabled or modify them as well. Can any one out their tell how i could
delete these jobs from the sql server tables in the database. The error
message that i get evertime i try modifying\ deleting anything on the job is
error 14274: Cannot add, update, or delete a job (or its steps or schedules)
that originated from an MSX server.
the job was not saved.
thanksThis problem could be attributable to the originating_server now differing
from the actual server name.
UPDATE msdb..sysjobs SET Originating_Server = Servername
The Microsoft KBase resolution is here :-
http://support.microsoft.com/default.aspx?scid=kb;en-us;Q281642
--
HTH. Ryan
"sameer" <sameer@.discussions.microsoft.com> wrote in message
news:03A8C8C8-2A05-4660-BD88-15EB2B74F164@.microsoft.com...
> hi all,
> we have renamed a server which had sql server on it, all the databases are
> still on it and their is no problem accessing them at all, and now after
> this
> the sql server jobs which were on this machine and were running before the
> name was changed are crashing everytime they run, when i tried deleted
> them
> since i dont need them any more it pops up and error, i am not even able
> to
> disabled or modify them as well. Can any one out their tell how i could
> delete these jobs from the sql server tables in the database. The error
> message that i get evertime i try modifying\ deleting anything on the job
> is
> error 14274: Cannot add, update, or delete a job (or its steps or
> schedules)
> that originated from an MSX server.
> the job was not saved.
> thanks

Deleting inaccessible Sql server jobs

hi all,
we have renamed a server which had sql server on it, all the databases are
still on it and their is no problem accessing them at all, and now after thi
s
the sql server jobs which were on this machine and were running before the
name was changed are crashing everytime they run, when i tried deleted them
since i dont need them any more it pops up and error, i am not even able to
disabled or modify them as well. Can any one out their tell how i could
delete these jobs from the sql server tables in the database. The error
message that i get evertime i try modifying\ deleting anything on the job is
error 14274: Cannot add, update, or delete a job (or its steps or schedules)
that originated from an MSX server.
the job was not saved.
thanksThis problem could be attributable to the originating_server now differing
from the actual server name.
UPDATE msdb..sysjobs SET Originating_Server = Servername
The Microsoft KBase resolution is here :-
http://support.microsoft.com/defaul...b;en-us;Q281642
--
HTH. Ryan
"sameer" <sameer@.discussions.microsoft.com> wrote in message
news:03A8C8C8-2A05-4660-BD88-15EB2B74F164@.microsoft.com...
> hi all,
> we have renamed a server which had sql server on it, all the databases are
> still on it and their is no problem accessing them at all, and now after
> this
> the sql server jobs which were on this machine and were running before the
> name was changed are crashing everytime they run, when i tried deleted
> them
> since i dont need them any more it pops up and error, i am not even able
> to
> disabled or modify them as well. Can any one out their tell how i could
> delete these jobs from the sql server tables in the database. The error
> message that i get evertime i try modifying\ deleting anything on the job
> is
> error 14274: Cannot add, update, or delete a job (or its steps or
> schedules)
> that originated from an MSX server.
> the job was not saved.
> thanks

Deleting inaccessible Sql server jobs

hi all,
we have renamed a server which had sql server on it, all the databases are
still on it and their is no problem accessing them at all, and now after this
the sql server jobs which were on this machine and were running before the
name was changed are crashing everytime they run, when i tried deleted them
since i dont need them any more it pops up and error, i am not even able to
disabled or modify them as well. Can any one out their tell how i could
delete these jobs from the sql server tables in the database. The error
message that i get evertime i try modifying\ deleting anything on the job is
error 14274: Cannot add, update, or delete a job (or its steps or schedules)
that originated from an MSX server.
the job was not saved.
thanks
This problem could be attributable to the originating_server now differing
from the actual server name.
UPDATE msdb..sysjobs SET Originating_Server = Servername
The Microsoft KBase resolution is here :-
http://support.microsoft.com/default...;en-us;Q281642
HTH. Ryan
"sameer" <sameer@.discussions.microsoft.com> wrote in message
news:03A8C8C8-2A05-4660-BD88-15EB2B74F164@.microsoft.com...
> hi all,
> we have renamed a server which had sql server on it, all the databases are
> still on it and their is no problem accessing them at all, and now after
> this
> the sql server jobs which were on this machine and were running before the
> name was changed are crashing everytime they run, when i tried deleted
> them
> since i dont need them any more it pops up and error, i am not even able
> to
> disabled or modify them as well. Can any one out their tell how i could
> delete these jobs from the sql server tables in the database. The error
> message that i get evertime i try modifying\ deleting anything on the job
> is
> error 14274: Cannot add, update, or delete a job (or its steps or
> schedules)
> that originated from an MSX server.
> the job was not saved.
> thanks

deleting backup history in order to allow for restore

Hello:
Is there an automated way of having SQL delete backup jobs? I ran
sp_delete_backuphistory against the msbd database in SQL Server 2000
8.00.2039 and I had to stop it because it was taking forever to run.
I'm surprised that SQL does not automatically delete backup history since
maintenance plans for automatically deleting backups. (Any relief in SQL
2005?)
The major reason that I ask about this is because when we conduct a manual
restore of a database, we cannot do so by right-clicking on that database in
Enterprise Manager. Enterprise Manager freezes when we choose All
Tasks...Restore. So, we end up having to instead run a script in Query
Analyzer to restore the database.
Someone on this message board told me to delete backup history. But, again,
that takes too long. And, when I tried to do a restore in Enterprise Manager
just now, I got the same result (though I did cancel the process).
Any ideas?
Thanks!
childofthe1980s
The first time you delete the history it will take a long time if it has
never been done before. Just let it run until it finishes otherwise you roll
it back and you are no better off than before. But once you clear out the
garbage that was in there it will only take a second or less to delete about
a weeks worth if you do it on a regular basis. So set up a scheduled job
that calls this once a week and pass in a datetime that leaves you the week
or two that you want to keep for history.
DECLARE @.Date DATETIME
SET @.Date = DATEADD(wk,-1,GETDATE())
EXEC [msdb].[dbo].[sp_delete_backuphistory] @.Date
In 2005 they have added a task for the MP to dod this but it does absolutely
nothing more than what I show above and still needs to be done regulary. The
problem is there is data in 3 tables and they are not properly indexed so a
delete on lots of data takes a long time.
Andrew J. Kelly SQL MVP
Solid Quality Mentors
"childofthe1980s" <childofthe1980s@.discussions.microsoft.com> wrote in
message news:851A896D-0D1E-4A07-9202-19AA98E8970D@.microsoft.com...
> Hello:
> Is there an automated way of having SQL delete backup jobs? I ran
> sp_delete_backuphistory against the msbd database in SQL Server 2000
> 8.00.2039 and I had to stop it because it was taking forever to run.
> I'm surprised that SQL does not automatically delete backup history since
> maintenance plans for automatically deleting backups. (Any relief in SQL
> 2005?)
> The major reason that I ask about this is because when we conduct a manual
> restore of a database, we cannot do so by right-clicking on that database
> in
> Enterprise Manager. Enterprise Manager freezes when we choose All
> Tasks...Restore. So, we end up having to instead run a script in Query
> Analyzer to restore the database.
> Someone on this message board told me to delete backup history. But,
> again,
> that takes too long. And, when I tried to do a restore in Enterprise
> Manager
> just now, I got the same result (though I did cancel the process).
> Any ideas?
> Thanks!
> childofthe1980s
>
>
>
|||Thanks, Andrew!
childofthe1980s
"Andrew J. Kelly" wrote:

> The first time you delete the history it will take a long time if it has
> never been done before. Just let it run until it finishes otherwise you roll
> it back and you are no better off than before. But once you clear out the
> garbage that was in there it will only take a second or less to delete about
> a weeks worth if you do it on a regular basis. So set up a scheduled job
> that calls this once a week and pass in a datetime that leaves you the week
> or two that you want to keep for history.
> DECLARE @.Date DATETIME
> SET @.Date = DATEADD(wk,-1,GETDATE())
> EXEC [msdb].[dbo].[sp_delete_backuphistory] @.Date
>
> In 2005 they have added a task for the MP to dod this but it does absolutely
> nothing more than what I show above and still needs to be done regulary. The
> problem is there is data in 3 tables and they are not properly indexed so a
> delete on lots of data takes a long time.
> --
> Andrew J. Kelly SQL MVP
> Solid Quality Mentors
>
> "childofthe1980s" <childofthe1980s@.discussions.microsoft.com> wrote in
> message news:851A896D-0D1E-4A07-9202-19AA98E8970D@.microsoft.com...
>

deleting backup history in order to allow for restore

Hello:
Is there an automated way of having SQL delete backup jobs? I ran
sp_delete_backuphistory against the msbd database in SQL Server 2000
8.00.2039 and I had to stop it because it was taking forever to run.
I'm surprised that SQL does not automatically delete backup history since
maintenance plans for automatically deleting backups. (Any relief in SQL
2005?)
The major reason that I ask about this is because when we conduct a manual
restore of a database, we cannot do so by right-clicking on that database in
Enterprise Manager. Enterprise Manager freezes when we choose All
Tasks...Restore. So, we end up having to instead run a script in Query
Analyzer to restore the database.
Someone on this message board told me to delete backup history. But, again,
that takes too long. And, when I tried to do a restore in Enterprise Manager
just now, I got the same result (though I did cancel the process).
Any ideas?
Thanks!
childofthe1980sThe first time you delete the history it will take a long time if it has
never been done before. Just let it run until it finishes otherwise you roll
it back and you are no better off than before. But once you clear out the
garbage that was in there it will only take a second or less to delete about
a weeks worth if you do it on a regular basis. So set up a scheduled job
that calls this once a week and pass in a datetime that leaves you the week
or two that you want to keep for history.
DECLARE @.Date DATETIME
SET @.Date = DATEADD(wk,-1,GETDATE())
EXEC [msdb].[dbo].[sp_delete_backuphistory] @.Date
In 2005 they have added a task for the MP to dod this but it does absolutely
nothing more than what I show above and still needs to be done regulary. The
problem is there is data in 3 tables and they are not properly indexed so a
delete on lots of data takes a long time.
--
Andrew J. Kelly SQL MVP
Solid Quality Mentors
"childofthe1980s" <childofthe1980s@.discussions.microsoft.com> wrote in
message news:851A896D-0D1E-4A07-9202-19AA98E8970D@.microsoft.com...
> Hello:
> Is there an automated way of having SQL delete backup jobs? I ran
> sp_delete_backuphistory against the msbd database in SQL Server 2000
> 8.00.2039 and I had to stop it because it was taking forever to run.
> I'm surprised that SQL does not automatically delete backup history since
> maintenance plans for automatically deleting backups. (Any relief in SQL
> 2005?)
> The major reason that I ask about this is because when we conduct a manual
> restore of a database, we cannot do so by right-clicking on that database
> in
> Enterprise Manager. Enterprise Manager freezes when we choose All
> Tasks...Restore. So, we end up having to instead run a script in Query
> Analyzer to restore the database.
> Someone on this message board told me to delete backup history. But,
> again,
> that takes too long. And, when I tried to do a restore in Enterprise
> Manager
> just now, I got the same result (though I did cancel the process).
> Any ideas?
> Thanks!
> childofthe1980s
>
>
>|||Thanks, Andrew!
childofthe1980s
"Andrew J. Kelly" wrote:
> The first time you delete the history it will take a long time if it has
> never been done before. Just let it run until it finishes otherwise you roll
> it back and you are no better off than before. But once you clear out the
> garbage that was in there it will only take a second or less to delete about
> a weeks worth if you do it on a regular basis. So set up a scheduled job
> that calls this once a week and pass in a datetime that leaves you the week
> or two that you want to keep for history.
> DECLARE @.Date DATETIME
> SET @.Date = DATEADD(wk,-1,GETDATE())
> EXEC [msdb].[dbo].[sp_delete_backuphistory] @.Date
>
> In 2005 they have added a task for the MP to dod this but it does absolutely
> nothing more than what I show above and still needs to be done regulary. The
> problem is there is data in 3 tables and they are not properly indexed so a
> delete on lots of data takes a long time.
> --
> Andrew J. Kelly SQL MVP
> Solid Quality Mentors
>
> "childofthe1980s" <childofthe1980s@.discussions.microsoft.com> wrote in
> message news:851A896D-0D1E-4A07-9202-19AA98E8970D@.microsoft.com...
> > Hello:
> >
> > Is there an automated way of having SQL delete backup jobs? I ran
> > sp_delete_backuphistory against the msbd database in SQL Server 2000
> > 8.00.2039 and I had to stop it because it was taking forever to run.
> >
> > I'm surprised that SQL does not automatically delete backup history since
> > maintenance plans for automatically deleting backups. (Any relief in SQL
> > 2005?)
> >
> > The major reason that I ask about this is because when we conduct a manual
> > restore of a database, we cannot do so by right-clicking on that database
> > in
> > Enterprise Manager. Enterprise Manager freezes when we choose All
> > Tasks...Restore. So, we end up having to instead run a script in Query
> > Analyzer to restore the database.
> >
> > Someone on this message board told me to delete backup history. But,
> > again,
> > that takes too long. And, when I tried to do a restore in Enterprise
> > Manager
> > just now, I got the same result (though I did cancel the process).
> >
> > Any ideas?
> >
> > Thanks!
> >
> > childofthe1980s
> >
> >
> >
> >
> >
>sql

Deleteing SQL Aent Jobs in SQL2005

Hi,
I have a situation where I had created a maintenance plan and edited the
resulting job. I had to delete the maintenance plan and job. In SQL2000 I
would delete the job first then the maintenance plan. I tried this is
SQL2005 and had errors. It referred to the DELETE statement conflicted with
REFERENCE constraint "FK_subplan_job_id". The conflict occurred in msdb
table dbo.sysmaintplan_subplans", column 'job_id'.
I could not delete the maintenance plan either. In the end I renamed the job
then I could delete the maintenance plan.
This is on SQL2005 SP1.
Thanks
ChrisI have same problem. Did you ever get a reply? If so, what do I do? I hav
e
several orphan jobs I cannot delete. Thanks for any info.|||DaveK,
I mentioned in my post how I fixed this. Nobody else replied.
Chris
"DaveK" <DaveK@.discussions.microsoft.com> wrote in message
news:79B9F73B-C3E3-47AB-8CCB-3AEA8EC02062@.microsoft.com...
>I have same problem. Did you ever get a reply? If so, what do I do? I
>have
> several orphan jobs I cannot delete. Thanks for any info.

Deleteing SQL Aent Jobs in SQL2005

Hi,
I have a situation where I had created a maintenance plan and edited the
resulting job. I had to delete the maintenance plan and job. In SQL2000 I
would delete the job first then the maintenance plan. I tried this is
SQL2005 and had errors. It referred to the DELETE statement conflicted with
REFERENCE constraint "FK_subplan_job_id". The conflict occurred in msdb
table dbo.sysmaintplan_subplans", column 'job_id'.
I could not delete the maintenance plan either. In the end I renamed the job
then I could delete the maintenance plan.
This is on SQL2005 SP1.
Thanks
Chris
I have same problem. Did you ever get a reply? If so, what do I do? I have
several orphan jobs I cannot delete. Thanks for any info.
|||DaveK,
I mentioned in my post how I fixed this. Nobody else replied.
Chris
"DaveK" <DaveK@.discussions.microsoft.com> wrote in message
news:79B9F73B-C3E3-47AB-8CCB-3AEA8EC02062@.microsoft.com...
>I have same problem. Did you ever get a reply? If so, what do I do? I
>have
> several orphan jobs I cannot delete. Thanks for any info.

Deleteing SQL Aent Jobs in SQL2005

Hi,
I have a situation where I had created a maintenance plan and edited the
resulting job. I had to delete the maintenance plan and job. In SQL2000 I
would delete the job first then the maintenance plan. I tried this is
SQL2005 and had errors. It referred to the DELETE statement conflicted with
REFERENCE constraint "FK_subplan_job_id". The conflict occurred in msdb
table dbo.sysmaintplan_subplans", column 'job_id'.
I could not delete the maintenance plan either. In the end I renamed the job
then I could delete the maintenance plan.
This is on SQL2005 SP1.
Thanks
Chris
I have same problem. Did you ever get a reply? If so, what do I do? I have
several orphan jobs I cannot delete. Thanks for any info.
|||DaveK,
I mentioned in my post how I fixed this. Nobody else replied.
Chris
"DaveK" <DaveK@.discussions.microsoft.com> wrote in message
news:79B9F73B-C3E3-47AB-8CCB-3AEA8EC02062@.microsoft.com...
>I have same problem. Did you ever get a reply? If so, what do I do? I
>have
> several orphan jobs I cannot delete. Thanks for any info.

Deleteing SQL Aent Jobs in SQL2005

Hi,
I have a situation where I had created a maintenance plan and edited the
resulting job. I had to delete the maintenance plan and job. In SQL2000 I
would delete the job first then the maintenance plan. I tried this is
SQL2005 and had errors. It referred to the DELETE statement conflicted with
REFERENCE constraint "FK_subplan_job_id". The conflict occurred in msdb
table dbo.sysmaintplan_subplans", column 'job_id'.
I could not delete the maintenance plan either. In the end I renamed the job
then I could delete the maintenance plan.
This is on SQL2005 SP1.
Thanks
ChrisI have same problem. Did you ever get a reply? If so, what do I do? I have
several orphan jobs I cannot delete. Thanks for any info.|||DaveK,
I mentioned in my post how I fixed this. Nobody else replied.
Chris
"DaveK" <DaveK@.discussions.microsoft.com> wrote in message
news:79B9F73B-C3E3-47AB-8CCB-3AEA8EC02062@.microsoft.com...
>I have same problem. Did you ever get a reply? If so, what do I do? I
>have
> several orphan jobs I cannot delete. Thanks for any info.

Delete Leftover SQL Jobs

Hi,
We have a SQL server that we moved from one physical server to another.
After the move we found that there are some SQL job in there that we no
longer need. Since they were created on the old server, Server IDs have now
changes and we can no longer delete them. Does anyone know how to delete
these jobs?
Thank you.
The easy (but unsupported way) is to change the name of the server in msdb.dbo.sysjobs:
http://www.karaszi.com/SQLServer/inf...erver_name.asp
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"Dragon" <baadil_nospam@.hotmail.com> wrote in message news:OBx4TKO$FHA.2812@.TK2MSFTNGP09.phx.gbl...
> Hi,
> We have a SQL server that we moved from one physical server to another. After the move we found
> that there are some SQL job in there that we no longer need. Since they were created on the old
> server, Server IDs have now changes and we can no longer delete them. Does anyone know how to
> delete these jobs?
> Thank you.
>
|||Thank you Tibor. Excellent information. :-)
"Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in
message news:%23A7LaxW$FHA.3804@.TK2MSFTNGP14.phx.gbl...
> The easy (but unsupported way) is to change the name of the server in
> msdb.dbo.sysjobs:
> http://www.karaszi.com/SQLServer/inf...erver_name.asp
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
> Blog: http://solidqualitylearning.com/blogs/tibor/
>
> "Dragon" <baadil_nospam@.hotmail.com> wrote in message
> news:OBx4TKO$FHA.2812@.TK2MSFTNGP09.phx.gbl...
>

Delete Leftover SQL Jobs

Hi,
We have a SQL server that we moved from one physical server to another.
After the move we found that there are some SQL job in there that we no
longer need. Since they were created on the old server, Server IDs have now
changes and we can no longer delete them. Does anyone know how to delete
these jobs?
Thank you.The easy (but unsupported way) is to change the name of the server in msdb.d
bo.sysjobs:
http://www.karaszi.com/SQLServer/in...server_name.asp
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"Dragon" <baadil_nospam@.hotmail.com> wrote in message news:OBx4TKO$FHA.2812@.TK2MSFTNGP09.phx
.gbl...
> Hi,
> We have a SQL server that we moved from one physical server to another. Af
ter the move we found
> that there are some SQL job in there that we no longer need. Since they we
re created on the old
> server, Server IDs have now changes and we can no longer delete them. Does
anyone know how to
> delete these jobs?
> Thank you.
>|||Thank you Tibor. Excellent information. :-)
"Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in
message news:%23A7LaxW$FHA.3804@.TK2MSFTNGP14.phx.gbl...
> The easy (but unsupported way) is to change the name of the server in
> msdb.dbo.sysjobs:
> http://www.karaszi.com/SQLServer/in...server_name.asp
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
> Blog: http://solidqualitylearning.com/blogs/tibor/
>
> "Dragon" <baadil_nospam@.hotmail.com> wrote in message
> news:OBx4TKO$FHA.2812@.TK2MSFTNGP09.phx.gbl...
>

Delete Leftover SQL Jobs

Hi,
We have a SQL server that we moved from one physical server to another.
After the move we found that there are some SQL job in there that we no
longer need. Since they were created on the old server, Server IDs have now
changes and we can no longer delete them. Does anyone know how to delete
these jobs?
Thank you.The easy (but unsupported way) is to change the name of the server in msdb.dbo.sysjobs:
http://www.karaszi.com/SQLServer/info_change_server_name.asp
--
Tibor Karaszi, SQL Server MVP
http://www.karaszi.com/sqlserver/default.asp
http://www.solidqualitylearning.com/
Blog: http://solidqualitylearning.com/blogs/tibor/
"Dragon" <baadil_nospam@.hotmail.com> wrote in message news:OBx4TKO$FHA.2812@.TK2MSFTNGP09.phx.gbl...
> Hi,
> We have a SQL server that we moved from one physical server to another. After the move we found
> that there are some SQL job in there that we no longer need. Since they were created on the old
> server, Server IDs have now changes and we can no longer delete them. Does anyone know how to
> delete these jobs?
> Thank you.
>|||Thank you Tibor. Excellent information. :-)
"Tibor Karaszi" <tibor_please.no.email_karaszi@.hotmail.nomail.com> wrote in
message news:%23A7LaxW$FHA.3804@.TK2MSFTNGP14.phx.gbl...
> The easy (but unsupported way) is to change the name of the server in
> msdb.dbo.sysjobs:
> http://www.karaszi.com/SQLServer/info_change_server_name.asp
> --
> Tibor Karaszi, SQL Server MVP
> http://www.karaszi.com/sqlserver/default.asp
> http://www.solidqualitylearning.com/
> Blog: http://solidqualitylearning.com/blogs/tibor/
>
> "Dragon" <baadil_nospam@.hotmail.com> wrote in message
> news:OBx4TKO$FHA.2812@.TK2MSFTNGP09.phx.gbl...
>> Hi,
>> We have a SQL server that we moved from one physical server to another.
>> After the move we found that there are some SQL job in there that we no
>> longer need. Since they were created on the old server, Server IDs have
>> now changes and we can no longer delete them. Does anyone know how to
>> delete these jobs?
>> Thank you.
>