Hello All,
We are in the process of migrating our SQLServer2000 production server to a
better hardware and Windows 2003. We have lot of DTS packages and SQL Jobs
that needs to be migrated as well. I can script the Jobs and run the script
on the new server and similarly I can save the DTS package on the new server.
Instead, Can I backup the msdb database and restore it on the new server. I
was wondering which method would be the best.
Thanks,
rgnRestoring MSDB is certainly an option but if you have anything that
references the original server name directly you may have to fix that.
These links may help:
http://vyaskn.tripod.com/moving_sql_server.htm Moving DBs
http://msdn2.microsoft.com/en-us/library/ms345408(en-US,SQL.90).aspx Moving
system dbs 2005
http://www.databasejournal.com/features/mssql/article.php/3379901 Moving
system DB's 2000
http://www.support.microsoft.com/?id=314546 Moving DB's between Servers
http://www.support.microsoft.com/?id=224071 Moving SQL Server Databases
to a New Location with Detach/Attach
http://www.support.microsoft.com/?id=221465 Using WITH MOVE in a Restore
http://www.sqlservercentral.com/columnists/cBunch/movingyouruserswiththeirdatabases.asp
Moving Users
http://www.support.microsoft.com/?id=246133 How To Transfer Logins and
Passwords Between SQL Servers
http://www.support.microsoft.com/?id=298897 Mapping Logins & SIDs after
a Restore
http://www.dbmaint.com/SyncSqlLogins.asp Utility to map logins to
users
http://www.support.microsoft.com/?id=168001 User Logon and/or Permission
Errors After Restoring Dump
http://www.support.microsoft.com/?id=240872 How to Resolve Permission
Issues When a Database Is Moved Between SQL Servers
http://www.sqlservercentral.com/scripts/scriptdetails.asp?scriptid=599
Restoring a .mdf
http://www.support.microsoft.com/?id=307775 Disaster Recovery Articles
for SQL Server
http://www.support.microsoft.com/?id=320125 Moving a Diagram
http://www.support.microsoft.com/?id=274463 Copy DB Wizard issues 2000
http://www.sqlservercentral.com/scripts/contributions/1598.asp Script
Roles and Permissions
--
Andrew J. Kelly SQL MVP
"rgn" <rgn@.discussions.microsoft.com> wrote in message
news:798481FC-6AD6-461C-A554-AF99EBD5B3E7@.microsoft.com...
> Hello All,
> We are in the process of migrating our SQLServer2000 production server to
> a
> better hardware and Windows 2003. We have lot of DTS packages and SQL Jobs
> that needs to be migrated as well. I can script the Jobs and run the
> script
> on the new server and similarly I can save the DTS package on the new
> server.
> Instead, Can I backup the msdb database and restore it on the new server.
> I
> was wondering which method would be the best.
> Thanks,
> rgn
Showing posts with label jobs. Show all posts
Showing posts with label jobs. Show all posts
Wednesday, March 28, 2012
Migrating DTS packages and SQL Jobs
Hello All,
We are in the process of migrating our SQLServer2000 production server to a
better hardware and Windows 2003. We have lot of DTS packages and SQL Jobs
that needs to be migrated as well. I can script the Jobs and run the script
on the new server and similarly I can save the DTS package on the new server
.
Instead, Can I backup the msdb database and restore it on the new server. I
was wondering which method would be the best.
Thanks,
rgnRestoring MSDB is certainly an option but if you have anything that
references the original server name directly you may have to fix that.
These links may help:
http://vyaskn.tripod.com/moving_sql_server.htm Moving DBs
http://msdn2.microsoft.com/en-us/library/ms345408(en-US,SQL.90).aspx Moving
system dbs 2005
http://www.databasejournal.com/feat...cle.php/3379901 Moving
system DB's 2000
http://www.support.microsoft.com/?id=314546 Moving DB's between Servers
http://www.support.microsoft.com/?id=224071 Moving SQL Server Databases
to a New Location with Detach/Attach
http://www.support.microsoft.com/?id=221465 Using WITH MOVE in a Restore
http://www.sqlservercentral.com/col...se
s.asp
Moving Users
http://www.support.microsoft.com/?id=246133 How To Transfer Logins and
Passwords Between SQL Servers
http://www.support.microsoft.com/?id=298897 Mapping Logins & SIDs after
a Restore
http://www.dbmaint.com/SyncSqlLogins.asp Utility to map logins to
users
http://www.support.microsoft.com/?id=168001 User Logon and/or Permission
Errors After Restoring Dump
http://www.support.microsoft.com/?id=240872 How to Resolve Permission
Issues When a Database Is Moved Between SQL Servers
http://www.sqlservercentral.com/scr...sp?scriptid=599
Restoring a .mdf
http://www.support.microsoft.com/?id=307775 Disaster Recovery Articles
for SQL Server
http://www.support.microsoft.com/?id=320125 Moving a Diagram
http://www.support.microsoft.com/?id=274463 Copy DB Wizard issues 2000
http://www.sqlservercentral.com/scr...utions/1598.asp Script
Roles and Permissions
Andrew J. Kelly SQL MVP
"rgn" <rgn@.discussions.microsoft.com> wrote in message
news:798481FC-6AD6-461C-A554-AF99EBD5B3E7@.microsoft.com...
> Hello All,
> We are in the process of migrating our SQLServer2000 production server to
> a
> better hardware and Windows 2003. We have lot of DTS packages and SQL Jobs
> that needs to be migrated as well. I can script the Jobs and run the
> script
> on the new server and similarly I can save the DTS package on the new
> server.
> Instead, Can I backup the msdb database and restore it on the new server.
> I
> was wondering which method would be the best.
> Thanks,
> rgn
We are in the process of migrating our SQLServer2000 production server to a
better hardware and Windows 2003. We have lot of DTS packages and SQL Jobs
that needs to be migrated as well. I can script the Jobs and run the script
on the new server and similarly I can save the DTS package on the new server
.
Instead, Can I backup the msdb database and restore it on the new server. I
was wondering which method would be the best.
Thanks,
rgnRestoring MSDB is certainly an option but if you have anything that
references the original server name directly you may have to fix that.
These links may help:
http://vyaskn.tripod.com/moving_sql_server.htm Moving DBs
http://msdn2.microsoft.com/en-us/library/ms345408(en-US,SQL.90).aspx Moving
system dbs 2005
http://www.databasejournal.com/feat...cle.php/3379901 Moving
system DB's 2000
http://www.support.microsoft.com/?id=314546 Moving DB's between Servers
http://www.support.microsoft.com/?id=224071 Moving SQL Server Databases
to a New Location with Detach/Attach
http://www.support.microsoft.com/?id=221465 Using WITH MOVE in a Restore
http://www.sqlservercentral.com/col...se
s.asp
Moving Users
http://www.support.microsoft.com/?id=246133 How To Transfer Logins and
Passwords Between SQL Servers
http://www.support.microsoft.com/?id=298897 Mapping Logins & SIDs after
a Restore
http://www.dbmaint.com/SyncSqlLogins.asp Utility to map logins to
users
http://www.support.microsoft.com/?id=168001 User Logon and/or Permission
Errors After Restoring Dump
http://www.support.microsoft.com/?id=240872 How to Resolve Permission
Issues When a Database Is Moved Between SQL Servers
http://www.sqlservercentral.com/scr...sp?scriptid=599
Restoring a .mdf
http://www.support.microsoft.com/?id=307775 Disaster Recovery Articles
for SQL Server
http://www.support.microsoft.com/?id=320125 Moving a Diagram
http://www.support.microsoft.com/?id=274463 Copy DB Wizard issues 2000
http://www.sqlservercentral.com/scr...utions/1598.asp Script
Roles and Permissions
Andrew J. Kelly SQL MVP
"rgn" <rgn@.discussions.microsoft.com> wrote in message
news:798481FC-6AD6-461C-A554-AF99EBD5B3E7@.microsoft.com...
> Hello All,
> We are in the process of migrating our SQLServer2000 production server to
> a
> better hardware and Windows 2003. We have lot of DTS packages and SQL Jobs
> that needs to be migrated as well. I can script the Jobs and run the
> script
> on the new server and similarly I can save the DTS package on the new
> server.
> Instead, Can I backup the msdb database and restore it on the new server.
> I
> was wondering which method would be the best.
> Thanks,
> rgn
Migrating DTS packages and SQL Jobs
Hello All,
We are in the process of migrating our SQLServer2000 production server to a
better hardware and Windows 2003. We have lot of DTS packages and SQL Jobs
that needs to be migrated as well. I can script the Jobs and run the script
on the new server and similarly I can save the DTS package on the new server.
Instead, Can I backup the msdb database and restore it on the new server. I
was wondering which method would be the best.
Thanks,
rgn
Restoring MSDB is certainly an option but if you have anything that
references the original server name directly you may have to fix that.
These links may help:
http://vyaskn.tripod.com/moving_sql_server.htm Moving DBs
http://msdn2.microsoft.com/en-us/library/ms345408(en-US,SQL.90).aspx Moving
system dbs 2005
http://www.databasejournal.com/features/mssql/article.php/3379901 Moving
system DB's 2000
http://www.support.microsoft.com/?id=314546 Moving DB's between Servers
http://www.support.microsoft.com/?id=224071 Moving SQL Server Databases
to a New Location with Detach/Attach
http://www.support.microsoft.com/?id=221465 Using WITH MOVE in a Restore
http://www.sqlservercentral.com/columnists/cBunch/movingyouruserswiththeirdatabases.asp
Moving Users
http://www.support.microsoft.com/?id=246133 How To Transfer Logins and
Passwords Between SQL Servers
http://www.support.microsoft.com/?id=298897 Mapping Logins & SIDs after
a Restore
http://www.dbmaint.com/SyncSqlLogins.asp Utility to map logins to
users
http://www.support.microsoft.com/?id=168001 User Logon and/or Permission
Errors After Restoring Dump
http://www.support.microsoft.com/?id=240872 How to Resolve Permission
Issues When a Database Is Moved Between SQL Servers
http://www.sqlservercentral.com/scripts/scriptdetails.asp?scriptid=599
Restoring a .mdf
http://www.support.microsoft.com/?id=307775 Disaster Recovery Articles
for SQL Server
http://www.support.microsoft.com/?id=320125 Moving a Diagram
http://www.support.microsoft.com/?id=274463 Copy DB Wizard issues 2000
http://www.sqlservercentral.com/scripts/contributions/1598.asp Script
Roles and Permissions
Andrew J. Kelly SQL MVP
"rgn" <rgn@.discussions.microsoft.com> wrote in message
news:798481FC-6AD6-461C-A554-AF99EBD5B3E7@.microsoft.com...
> Hello All,
> We are in the process of migrating our SQLServer2000 production server to
> a
> better hardware and Windows 2003. We have lot of DTS packages and SQL Jobs
> that needs to be migrated as well. I can script the Jobs and run the
> script
> on the new server and similarly I can save the DTS package on the new
> server.
> Instead, Can I backup the msdb database and restore it on the new server.
> I
> was wondering which method would be the best.
> Thanks,
> rgn
sql
We are in the process of migrating our SQLServer2000 production server to a
better hardware and Windows 2003. We have lot of DTS packages and SQL Jobs
that needs to be migrated as well. I can script the Jobs and run the script
on the new server and similarly I can save the DTS package on the new server.
Instead, Can I backup the msdb database and restore it on the new server. I
was wondering which method would be the best.
Thanks,
rgn
Restoring MSDB is certainly an option but if you have anything that
references the original server name directly you may have to fix that.
These links may help:
http://vyaskn.tripod.com/moving_sql_server.htm Moving DBs
http://msdn2.microsoft.com/en-us/library/ms345408(en-US,SQL.90).aspx Moving
system dbs 2005
http://www.databasejournal.com/features/mssql/article.php/3379901 Moving
system DB's 2000
http://www.support.microsoft.com/?id=314546 Moving DB's between Servers
http://www.support.microsoft.com/?id=224071 Moving SQL Server Databases
to a New Location with Detach/Attach
http://www.support.microsoft.com/?id=221465 Using WITH MOVE in a Restore
http://www.sqlservercentral.com/columnists/cBunch/movingyouruserswiththeirdatabases.asp
Moving Users
http://www.support.microsoft.com/?id=246133 How To Transfer Logins and
Passwords Between SQL Servers
http://www.support.microsoft.com/?id=298897 Mapping Logins & SIDs after
a Restore
http://www.dbmaint.com/SyncSqlLogins.asp Utility to map logins to
users
http://www.support.microsoft.com/?id=168001 User Logon and/or Permission
Errors After Restoring Dump
http://www.support.microsoft.com/?id=240872 How to Resolve Permission
Issues When a Database Is Moved Between SQL Servers
http://www.sqlservercentral.com/scripts/scriptdetails.asp?scriptid=599
Restoring a .mdf
http://www.support.microsoft.com/?id=307775 Disaster Recovery Articles
for SQL Server
http://www.support.microsoft.com/?id=320125 Moving a Diagram
http://www.support.microsoft.com/?id=274463 Copy DB Wizard issues 2000
http://www.sqlservercentral.com/scripts/contributions/1598.asp Script
Roles and Permissions
Andrew J. Kelly SQL MVP
"rgn" <rgn@.discussions.microsoft.com> wrote in message
news:798481FC-6AD6-461C-A554-AF99EBD5B3E7@.microsoft.com...
> Hello All,
> We are in the process of migrating our SQLServer2000 production server to
> a
> better hardware and Windows 2003. We have lot of DTS packages and SQL Jobs
> that needs to be migrated as well. I can script the Jobs and run the
> script
> on the new server and similarly I can save the DTS package on the new
> server.
> Instead, Can I backup the msdb database and restore it on the new server.
> I
> was wondering which method would be the best.
> Thanks,
> rgn
sql
Migrating DTS packages
Is there anyway to copy all the DTS packages and jobs in one step from one server to another. I usvally copy one DTS package at a time. As our packages count grown bigger, it became a painful process.
If anyone knows a way to copy these packages and jobs in one then it would be very helpful.
ThanksI don't think you can for DTS: Steps I have used in the past:
Save DTS package to hard drive:
Save DTS package as file on the disk, then copy this file on the target SQL Server and load this DTS package on the target machine. Dont forget to save in SQL Server.
Or...
Run DTS Export Wizard, and transfer this select statement:
SELECT * FROM sysdtspackages WHERE name = 'DTSPackageName'
from the msdb database on the source server to the msdb database on the destination server to transfer the DTSPackageName package.
You may be able to add multi packageName, I have never play around with the code. (Maybe someone else will have an idea)
And...
As for jobs you can create a DTS package and under Task select 15 - Transfer job task and follow the steps. You can do all of your jobs at once.
Hope it works out for you.
Thanks
Lystra|||As for the DTS packages go to http://www.sqldts.com/default.aspx?242 This is a free tool to migrate the DTS packages in one step.
If anyone knows a way to copy these packages and jobs in one then it would be very helpful.
ThanksI don't think you can for DTS: Steps I have used in the past:
Save DTS package to hard drive:
Save DTS package as file on the disk, then copy this file on the target SQL Server and load this DTS package on the target machine. Dont forget to save in SQL Server.
Or...
Run DTS Export Wizard, and transfer this select statement:
SELECT * FROM sysdtspackages WHERE name = 'DTSPackageName'
from the msdb database on the source server to the msdb database on the destination server to transfer the DTSPackageName package.
You may be able to add multi packageName, I have never play around with the code. (Maybe someone else will have an idea)
And...
As for jobs you can create a DTS package and under Task select 15 - Transfer job task and follow the steps. You can do all of your jobs at once.
Hope it works out for you.
Thanks
Lystra|||As for the DTS packages go to http://www.sqldts.com/default.aspx?242 This is a free tool to migrate the DTS packages in one step.
Wednesday, March 21, 2012
Migrate Jobs, DTS and Alerts
Hello,
I need to migrate all my databases to another database
server, can you tell me how can i migrate all the existing
Jobs, DTS's and Alerts sucefully from one server to
another with the minimum effort?
The scheduled DTS's will function on the destination
server?
Thanks,
Best regardsI just went through this. I migrated all my packages using SQL_DMO. I
wrote some code that processed through each DTS package using the DTS
Package Object. The processing I did was to change connection strings, or
any references to server specific stuff, and then saved them onto the new
servers. Did a similar things with the SQL Agent Jobs, and Alerts.
----
----
--
Need SQL Server Examples check out my website at
http://www.geocities.com/sqlserverexamples
"CC&JM" <anonymous@.discussions.microsoft.com> wrote in message
news:2478201c45f79$57739290$a501280a@.phx
.gbl...
> Hello,
> I need to migrate all my databases to another database
> server, can you tell me how can i migrate all the existing
> Jobs, DTS's and Alerts sucefully from one server to
> another with the minimum effort?
> The scheduled DTS's will function on the destination
> server?
> Thanks,
> Best regards
>
I need to migrate all my databases to another database
server, can you tell me how can i migrate all the existing
Jobs, DTS's and Alerts sucefully from one server to
another with the minimum effort?
The scheduled DTS's will function on the destination
server?
Thanks,
Best regardsI just went through this. I migrated all my packages using SQL_DMO. I
wrote some code that processed through each DTS package using the DTS
Package Object. The processing I did was to change connection strings, or
any references to server specific stuff, and then saved them onto the new
servers. Did a similar things with the SQL Agent Jobs, and Alerts.
----
----
--
Need SQL Server Examples check out my website at
http://www.geocities.com/sqlserverexamples
"CC&JM" <anonymous@.discussions.microsoft.com> wrote in message
news:2478201c45f79$57739290$a501280a@.phx
.gbl...
> Hello,
> I need to migrate all my databases to another database
> server, can you tell me how can i migrate all the existing
> Jobs, DTS's and Alerts sucefully from one server to
> another with the minimum effort?
> The scheduled DTS's will function on the destination
> server?
> Thanks,
> Best regards
>
Migrate Jobs, DTS and Alerts
Hello,
I need to migrate all my databases to another database
server, can you tell me how can i migrate all the existing
Jobs, DTS's and Alerts sucefully from one server to
another with the minimum effort?
The scheduled DTS's will function on the destination
server?
Thanks,
Best regards
I just went through this. I migrated all my packages using SQL_DMO. I
wrote some code that processed through each DTS package using the DTS
Package Object. The processing I did was to change connection strings, or
any references to server specific stuff, and then saved them onto the new
servers. Did a similar things with the SQL Agent Jobs, and Alerts.
----
Need SQL Server Examples check out my website at
http://www.geocities.com/sqlserverexamples
"CC&JM" <anonymous@.discussions.microsoft.com> wrote in message
news:2478201c45f79$57739290$a501280a@.phx.gbl...
> Hello,
> I need to migrate all my databases to another database
> server, can you tell me how can i migrate all the existing
> Jobs, DTS's and Alerts sucefully from one server to
> another with the minimum effort?
> The scheduled DTS's will function on the destination
> server?
> Thanks,
> Best regards
>
I need to migrate all my databases to another database
server, can you tell me how can i migrate all the existing
Jobs, DTS's and Alerts sucefully from one server to
another with the minimum effort?
The scheduled DTS's will function on the destination
server?
Thanks,
Best regards
I just went through this. I migrated all my packages using SQL_DMO. I
wrote some code that processed through each DTS package using the DTS
Package Object. The processing I did was to change connection strings, or
any references to server specific stuff, and then saved them onto the new
servers. Did a similar things with the SQL Agent Jobs, and Alerts.
----
Need SQL Server Examples check out my website at
http://www.geocities.com/sqlserverexamples
"CC&JM" <anonymous@.discussions.microsoft.com> wrote in message
news:2478201c45f79$57739290$a501280a@.phx.gbl...
> Hello,
> I need to migrate all my databases to another database
> server, can you tell me how can i migrate all the existing
> Jobs, DTS's and Alerts sucefully from one server to
> another with the minimum effort?
> The scheduled DTS's will function on the destination
> server?
> Thanks,
> Best regards
>
Migrate Jobs, DTS and Alerts
Hello,
I need to migrate all my databases to another database
server, can you tell me how can i migrate all the existing
Jobs, DTS's and Alerts sucefully from one server to
another with the minimum effort?
The scheduled DTS's will function on the destination
server?
Thanks,
Best regardsI just went through this. I migrated all my packages using SQL_DMO. I
wrote some code that processed through each DTS package using the DTS
Package Object. The processing I did was to change connection strings, or
any references to server specific stuff, and then saved them onto the new
servers. Did a similar things with the SQL Agent Jobs, and Alerts.
--
----
----
--
Need SQL Server Examples check out my website at
http://www.geocities.com/sqlserverexamples
"CC&JM" <anonymous@.discussions.microsoft.com> wrote in message
news:2478201c45f79$57739290$a501280a@.phx.gbl...
> Hello,
> I need to migrate all my databases to another database
> server, can you tell me how can i migrate all the existing
> Jobs, DTS's and Alerts sucefully from one server to
> another with the minimum effort?
> The scheduled DTS's will function on the destination
> server?
> Thanks,
> Best regards
>sql
I need to migrate all my databases to another database
server, can you tell me how can i migrate all the existing
Jobs, DTS's and Alerts sucefully from one server to
another with the minimum effort?
The scheduled DTS's will function on the destination
server?
Thanks,
Best regardsI just went through this. I migrated all my packages using SQL_DMO. I
wrote some code that processed through each DTS package using the DTS
Package Object. The processing I did was to change connection strings, or
any references to server specific stuff, and then saved them onto the new
servers. Did a similar things with the SQL Agent Jobs, and Alerts.
--
----
----
--
Need SQL Server Examples check out my website at
http://www.geocities.com/sqlserverexamples
"CC&JM" <anonymous@.discussions.microsoft.com> wrote in message
news:2478201c45f79$57739290$a501280a@.phx.gbl...
> Hello,
> I need to migrate all my databases to another database
> server, can you tell me how can i migrate all the existing
> Jobs, DTS's and Alerts sucefully from one server to
> another with the minimum effort?
> The scheduled DTS's will function on the destination
> server?
> Thanks,
> Best regards
>sql
Migrate jobs from production to backup
The backup server is using the agent to run log shipping. If I were to
migrate jobs prior to a disaster, the agent would run them. Assuming I can
turn them off so that having them run is not an issue, migrating them one at
a time is tedious.
Is there a way to mass migrate the jobs from one server to the other?
(packages are already migrated)
If such a thing as a mass import of the jobs is available, will the job
migration automatically schedule the packages or will it be necessary to
reschedule them (assuming a disaster event occurs and log-shipping is the
backup solution).
Regards,
Jamie
Hi
"thejamie" wrote:
> The backup server is using the agent to run log shipping. If I were to
> migrate jobs prior to a disaster, the agent would run them. Assuming I can
> turn them off so that having them run is not an issue, migrating them one at
> a time is tedious.
> Is there a way to mass migrate the jobs from one server to the other?
> (packages are already migrated)
>
As described in http://support.microsoft.com/kb/314546 you can script all
jobs.
> If such a thing as a mass import of the jobs is available, will the job
> migration automatically schedule the packages or will it be necessary to
> reschedule them (assuming a disaster event occurs and log-shipping is the
> backup solution).
>
Scripting will re-create the same schedules. The jobs should be enabled when
you are scripting them if you don't want to change them on the destination
server.
> --
> Regards,
> Jamie
John
|||I hadn't noticed before, but there appears to be a wizard in SQL 2005 for
this. We have our production running on 2000 and with disk space at a
premium and backup time stretched to the limit, we needed to start
compressing backups and decided to buy a package. It works great. I am
impressed to see that the 2005 version already does this. Elated actually.
Regards,
Jamie
"John Bell" wrote:
> Hi
> "thejamie" wrote:
> As described in http://support.microsoft.com/kb/314546 you can script all
> jobs.
>
> Scripting will re-create the same schedules. The jobs should be enabled when
> you are scripting them if you don't want to change them on the destination
> server.
>
> John
migrate jobs prior to a disaster, the agent would run them. Assuming I can
turn them off so that having them run is not an issue, migrating them one at
a time is tedious.
Is there a way to mass migrate the jobs from one server to the other?
(packages are already migrated)
If such a thing as a mass import of the jobs is available, will the job
migration automatically schedule the packages or will it be necessary to
reschedule them (assuming a disaster event occurs and log-shipping is the
backup solution).
Regards,
Jamie
Hi
"thejamie" wrote:
> The backup server is using the agent to run log shipping. If I were to
> migrate jobs prior to a disaster, the agent would run them. Assuming I can
> turn them off so that having them run is not an issue, migrating them one at
> a time is tedious.
> Is there a way to mass migrate the jobs from one server to the other?
> (packages are already migrated)
>
As described in http://support.microsoft.com/kb/314546 you can script all
jobs.
> If such a thing as a mass import of the jobs is available, will the job
> migration automatically schedule the packages or will it be necessary to
> reschedule them (assuming a disaster event occurs and log-shipping is the
> backup solution).
>
Scripting will re-create the same schedules. The jobs should be enabled when
you are scripting them if you don't want to change them on the destination
server.
> --
> Regards,
> Jamie
John
|||I hadn't noticed before, but there appears to be a wizard in SQL 2005 for
this. We have our production running on 2000 and with disk space at a
premium and backup time stretched to the limit, we needed to start
compressing backups and decided to buy a package. It works great. I am
impressed to see that the 2005 version already does this. Elated actually.
Regards,
Jamie
"John Bell" wrote:
> Hi
> "thejamie" wrote:
> As described in http://support.microsoft.com/kb/314546 you can script all
> jobs.
>
> Scripting will re-create the same schedules. The jobs should be enabled when
> you are scripting them if you don't want to change them on the destination
> server.
>
> John
Migrate jobs from production to backup
The backup server is using the agent to run log shipping. If I were to
migrate jobs prior to a disaster, the agent would run them. Assuming I can
turn them off so that having them run is not an issue, migrating them one at
a time is tedious.
Is there a way to mass migrate the jobs from one server to the other?
(packages are already migrated)
If such a thing as a mass import of the jobs is available, will the job
migration automatically schedule the packages or will it be necessary to
reschedule them (assuming a disaster event occurs and log-shipping is the
backup solution).
Regards,
JamieHi
"thejamie" wrote:
> The backup server is using the agent to run log shipping. If I were to
> migrate jobs prior to a disaster, the agent would run them. Assuming I c
an
> turn them off so that having them run is not an issue, migrating them one
at
> a time is tedious.
> Is there a way to mass migrate the jobs from one server to the other?
> (packages are already migrated)
>
As described in http://support.microsoft.com/kb/314546 you can script all
jobs.
> If such a thing as a mass import of the jobs is available, will the job
> migration automatically schedule the packages or will it be necessary to
> reschedule them (assuming a disaster event occurs and log-shipping is the
> backup solution).
>
Scripting will re-create the same schedules. The jobs should be enabled when
you are scripting them if you don't want to change them on the destination
server.
> --
> Regards,
> Jamie
John|||I hadn't noticed before, but there appears to be a wizard in SQL 2005 for
this. We have our production running on 2000 and with disk space at a
premium and backup time stretched to the limit, we needed to start
compressing backups and decided to buy a package. It works great. I am
impressed to see that the 2005 version already does this. Elated actually.
--
Regards,
Jamie
"John Bell" wrote:
> Hi
> "thejamie" wrote:
>
> As described in http://support.microsoft.com/kb/314546 you can script all
> jobs.
>
> Scripting will re-create the same schedules. The jobs should be enabled wh
en
> you are scripting them if you don't want to change them on the destination
> server.
>
> John
migrate jobs prior to a disaster, the agent would run them. Assuming I can
turn them off so that having them run is not an issue, migrating them one at
a time is tedious.
Is there a way to mass migrate the jobs from one server to the other?
(packages are already migrated)
If such a thing as a mass import of the jobs is available, will the job
migration automatically schedule the packages or will it be necessary to
reschedule them (assuming a disaster event occurs and log-shipping is the
backup solution).
Regards,
JamieHi
"thejamie" wrote:
> The backup server is using the agent to run log shipping. If I were to
> migrate jobs prior to a disaster, the agent would run them. Assuming I c
an
> turn them off so that having them run is not an issue, migrating them one
at
> a time is tedious.
> Is there a way to mass migrate the jobs from one server to the other?
> (packages are already migrated)
>
As described in http://support.microsoft.com/kb/314546 you can script all
jobs.
> If such a thing as a mass import of the jobs is available, will the job
> migration automatically schedule the packages or will it be necessary to
> reschedule them (assuming a disaster event occurs and log-shipping is the
> backup solution).
>
Scripting will re-create the same schedules. The jobs should be enabled when
you are scripting them if you don't want to change them on the destination
server.
> --
> Regards,
> Jamie
John|||I hadn't noticed before, but there appears to be a wizard in SQL 2005 for
this. We have our production running on 2000 and with disk space at a
premium and backup time stretched to the limit, we needed to start
compressing backups and decided to buy a package. It works great. I am
impressed to see that the 2005 version already does this. Elated actually.
--
Regards,
Jamie
"John Bell" wrote:
> Hi
> "thejamie" wrote:
>
> As described in http://support.microsoft.com/kb/314546 you can script all
> jobs.
>
> Scripting will re-create the same schedules. The jobs should be enabled wh
en
> you are scripting them if you don't want to change them on the destination
> server.
>
> John
Subscribe to:
Posts (Atom)