I need to move all my jobs on SQL 2000 and create them on SQL 2005, my
question what would the best and quickest way.?
and is there a way to script them all at once instead of one at the time.
Thanks
Hi
"msnews.microsoft.com" wrote:
> I need to move all my jobs on SQL 2000 and create them on SQL 2005, my
> question what would the best and quickest way.?
> and is there a way to script them all at once instead of one at the time.
> Thanks
>
See http://support.microsoft.com/kb/314546 on how to move jobs. Your job
scripts should be held in a Source Code management system along with all your
other DDL.
There are scripts to move logins and you will need to associate orphaned
users to logins.
Make sure you database are SQL 2005 compatible by using the Upgrade advisor
http://tinyurl.com/zt3a6 and change the compatibility mode of the
restored/reattached database to SQL 90. Other actions would include
rebuilding indexes, statistics and updating usage see
http://msdn2.microsoft.com/en-us/library/ms144267.aspx
John
Showing posts with label quickest. Show all posts
Showing posts with label quickest. Show all posts
Monday, March 12, 2012
Script Jobs
I need to move all my jobs on SQL 2000 and create them on SQL 2005, my
question what would the best and quickest way.?
and is there a way to script them all at once instead of one at the time.
ThanksHi
"msnews.microsoft.com" wrote:
> I need to move all my jobs on SQL 2000 and create them on SQL 2005, my
> question what would the best and quickest way.?
> and is there a way to script them all at once instead of one at the time.
> Thanks
>
See http://support.microsoft.com/kb/314546 on how to move jobs. Your job
scripts should be held in a Source Code management system along with all your
other DDL.
There are scripts to move logins and you will need to associate orphaned
users to logins.
Make sure you database are SQL 2005 compatible by using the Upgrade advisor
http://tinyurl.com/zt3a6 and change the compatibility mode of the
restored/reattached database to SQL 90. Other actions would include
rebuilding indexes, statistics and updating usage see
http://msdn2.microsoft.com/en-us/library/ms144267.aspx
John
question what would the best and quickest way.?
and is there a way to script them all at once instead of one at the time.
ThanksHi
"msnews.microsoft.com" wrote:
> I need to move all my jobs on SQL 2000 and create them on SQL 2005, my
> question what would the best and quickest way.?
> and is there a way to script them all at once instead of one at the time.
> Thanks
>
See http://support.microsoft.com/kb/314546 on how to move jobs. Your job
scripts should be held in a Source Code management system along with all your
other DDL.
There are scripts to move logins and you will need to associate orphaned
users to logins.
Make sure you database are SQL 2005 compatible by using the Upgrade advisor
http://tinyurl.com/zt3a6 and change the compatibility mode of the
restored/reattached database to SQL 90. Other actions would include
rebuilding indexes, statistics and updating usage see
http://msdn2.microsoft.com/en-us/library/ms144267.aspx
John
Script Jobs
I need to move all my jobs on SQL 2000 and create them on SQL 2005, my
question what would the best and quickest way.?
and is there a way to script them all at once instead of one at the time.
ThanksHi
"msnews.microsoft.com" wrote:
> I need to move all my jobs on SQL 2000 and create them on SQL 2005, my
> question what would the best and quickest way.?
> and is there a way to script them all at once instead of one at the time.
> Thanks
>
See http://support.microsoft.com/kb/314546 on how to move jobs. Your job
scripts should be held in a Source Code management system along with all you
r
other DDL.
There are scripts to move logins and you will need to associate orphaned
users to logins.
Make sure you database are SQL 2005 compatible by using the Upgrade advisor
http://tinyurl.com/zt3a6 and change the compatibility mode of the
restored/reattached database to SQL 90. Other actions would include
rebuilding indexes, statistics and updating usage see
http://msdn2.microsoft.com/en-us/library/ms144267.aspx
John
question what would the best and quickest way.?
and is there a way to script them all at once instead of one at the time.
ThanksHi
"msnews.microsoft.com" wrote:
> I need to move all my jobs on SQL 2000 and create them on SQL 2005, my
> question what would the best and quickest way.?
> and is there a way to script them all at once instead of one at the time.
> Thanks
>
See http://support.microsoft.com/kb/314546 on how to move jobs. Your job
scripts should be held in a Source Code management system along with all you
r
other DDL.
There are scripts to move logins and you will need to associate orphaned
users to logins.
Make sure you database are SQL 2005 compatible by using the Upgrade advisor
http://tinyurl.com/zt3a6 and change the compatibility mode of the
restored/reattached database to SQL 90. Other actions would include
rebuilding indexes, statistics and updating usage see
http://msdn2.microsoft.com/en-us/library/ms144267.aspx
John
Subscribe to:
Posts (Atom)