February 23, 2009 at 10:17 pm
Hi All,
I want to migrate from sql 2000 enterprise edition to sql 2005 enterprise edition. I want to transfer all of my databases, logins, jobs, DTS packages.
Main question i want to ask is do i have to migrate the system database as well? If i want to migrate all of the above things.
Thank you very much for ur time in advance.
February 24, 2009 at 1:54 am
You may want to check this step-by-step guide to migrate from SS2000 to SS2005 http://searchsqlserver.techtarget.com/generic/0,295582,sid87_gci1194265,00.html#
_____________________________________
Pablo (Paul) Berzukov
Author of Understanding Database Administration available at Amazon and other bookstores.
Disclaimer: Advice is provided to the best of my knowledge but no implicit or explicit warranties are provided. Since the advisor explicitly encourages testing any and all suggestions on a test non-production environment advisor should not held liable or responsible for any actions taken based on the given advice.February 24, 2009 at 2:34 am
So SQL 200 to 2005 migration is possible? 😀
Regards,
Sakthi
My Blog -> http://www.sqlserverdba.co.cc
February 24, 2009 at 7:23 am
Sakthivel Chidambaram (2/24/2009)
So SQL 200 to 2005 migration is possible? 😀
Migration from SQL 2000 to a new version (2005 or 2008) is possible, but if you want to migrate from SQL 2005 back to SQL 2000 you'll have to script the database en ex- and import data. Migration to a previous version is NOT possible.
February 24, 2009 at 8:03 am
HanShi (2/24/2009)
Sakthivel Chidambaram (2/24/2009)
So SQL 200 to 2005 migration is possible? 😀Migration from SQL 2000 to a new version (2005 or 2008) is possible, but if you want to migrate from SQL 2005 back to SQL 2000 you'll have to script the database en ex- and import data. Migration to a previous version is NOT possible.
Okay, let me jump in just for the fun of it.
You do not "migrate" from SS2000 to SS2005, you "upgrade" which is something totally different.
On the same line I've to agree there is no supported "downgrade" process but... who cares? poster didn't asked that question 😛
_____________________________________
Pablo (Paul) Berzukov
Author of Understanding Database Administration available at Amazon and other bookstores.
Disclaimer: Advice is provided to the best of my knowledge but no implicit or explicit warranties are provided. Since the advisor explicitly encourages testing any and all suggestions on a test non-production environment advisor should not held liable or responsible for any actions taken based on the given advice.February 24, 2009 at 8:50 am
Actually, MS does refer to side-by-side upgrade as "migration". Zombi, if you're really talking about installing a SQL 2005 intance and migrating databases to it with backup/restore or detach/attach, then no, you can't migrate system databases. Only user databases can be migrated that way.
Greg
February 24, 2009 at 9:10 am
zombi (2/23/2009)
Hi All,Main question i want to ask is do i have to migrate the system database as well? If i want to migrate all of the above things.
Thank you very much for ur time in advance.
DTS Migration:
By migrating the system databases you can't get the DTS packages in 2005, because 2005 you have SSIS.
Here you have to redesign complex DTS packages like if your DTS Package has VB or JAVA script task.
Login migration:
I do not think it is possible to get the logins by restoring the 2000 master db database on 2005.
Jobs Migration:
You can script out all the jobs in 2000 and execute on 2005, here you need to test and verify all the jobs.
Rajesh Kasturi
February 24, 2009 at 9:40 pm
Thanks for ur sincere answer.
The question i asked is because MSDB database contains job information and master database contains other information. so if i migrate sql agent jobs and logins do i have to change anything in system database? or master or msdb database will automatically will pick it up?
Once again thanks for ur time.
February 24, 2009 at 10:25 pm
Rajesh kasturi (2/24/2009)
DTS Migration:By migrating the system databases you can't get the DTS packages in 2005, because 2005 you have SSIS.
Here you have to redesign complex DTS packages like if your DTS Package has VB or JAVA script task.
You can use "DTS Designer Components" to run your existing 2000 DTS packages in a 2005 environment. It takes 1 minute to download & install.
You can also use this great tool as mentioned in another thread to import the DTS packages from 2000 to 2005. http://www.sqldts.com/242.aspx
Sakthivel Chidambaram (2/24/2009)
So SQL 200 to 2005 migration is possible? 😀
That's a very old version ! Reminds me of when I was programming on the AS/400 and got a recruiter call about a job on the AS/4000 !!
February 25, 2009 at 3:15 am
Sakthivel Chidambaram (2/24/2009)
So SQL 200 to 2005 migration is possible? 😀
That's a very old version ! Reminds me of when I was programming on the AS/400 and got a recruiter call about a job on the AS/4000 !![/quote]
Not to mention the job post asking for "... ten years hands-on experience on HAL-9000 systems preferred." 😛
_____________________________________
Pablo (Paul) Berzukov
Author of Understanding Database Administration available at Amazon and other bookstores.
Disclaimer: Advice is provided to the best of my knowledge but no implicit or explicit warranties are provided. Since the advisor explicitly encourages testing any and all suggestions on a test non-production environment advisor should not held liable or responsible for any actions taken based on the given advice.February 25, 2009 at 10:50 am
zombi (2/24/2009)
Thanks for ur sincere answer.The question i asked is because MSDB database contains job information and master database contains other information. so if i migrate sql agent jobs and logins do i have to change anything in system database? or master or msdb database will automatically will pick it up?
Once again thanks for ur time.
If you upgrade in place, you won't have to do anything to msdb and master in SQL 2005. If you do a side-by-side upgrade, you'll have to script jobs and logins in SQL 2000 and run the scripts in SQL 2005 to create them. You'll have to export DTS packages from SQL 2000 and import them in SQL 2005. DTSBackup2000, mentioned by Homebrew01, is a great help with packages.
Greg
February 25, 2009 at 3:59 pm
I did an "in place" upgrade in place at my previous job and it was very easy. Now I'm doing "side-by_side" because we're moving to new hardware at the same time. There is some risk in doing the "in place" upgrade because if something goes terribly wrong, you will have to rebuild SQL. With the side-by-side, your original server stays intact while you migrate to another server or instance, although you now have a new server or instance name to deal with also.
Thanks to Greg for making me aware of the DTS tool .... worked great
Viewing 12 posts - 1 through 11 (of 11 total)
You must be logged in to reply to this topic. Login to reply