May 9, 2009 at 12:18 am
hi,
I am trying to move Master database from the 2000 to 2005.
without stop the production server is it possible or not?
if possible give me some guidance
Ramaprasad.
May 9, 2009 at 2:12 am
Don't try. The system databases shouldn't be moved from one version to another. It's really asking for problems.
Script out whatever it is in the master database that you want (logins, roles, server permissions, linked servers) and then run those scripts against the 2005 server. Same with msdb.
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
May 10, 2009 at 2:44 am
prasadrandi (5/9/2009)
hi,I am trying to move Master database from the 2000 to 2005.
without stop the production server is it possible or not?
if possible give me some guidance
Ramaprasad.
But why want to do that?, IF it is for logins follows gilas method.
May 11, 2009 at 2:27 am
Take Gila's advice. If you do this you will break SQL Server.
Original author: https://github.com/SQL-FineBuild/Common/wiki/ 1-click install and best practice configuration of SQL Server 2019, 2017 2016, 2014, 2012, 2008 R2, 2008 and 2005.
When I give food to the poor they call me a saint. When I ask why they are poor they call me a communist - Archbishop Hélder Câmara
July 1, 2010 at 4:24 pm
would you send me a link to show how to script against master database ( in sql 2000 ) to collect data and then restore it to sql 2005 or sql 2008
July 1, 2010 at 10:31 pm
mitra.zaimi (7/1/2010)
would you send me a link to show how to script against master database ( in sql 2000 ) to collect data and then restore it to sql 2005 or sql 2008
Errrr... Links to script? Script data?
To script most objects in SQL 2000 you can Use Enterprise Manager, Right Click and select generate script.
However if you are asking questions like this I would seriously consider asking someone with more experience to migrate the system from SQL 2000 to SQL 2005 or 2008. This is not really a task for the faint hearted. A number of features are being depricated and you could end up with serious issues.
Have you at least used the Upgrade Advisor to check that the databases can actually be upgraded?
Also do you want objects or data? Besides things like logins, linked servers and the like, you shouldn't have anything in Master that you need to migrate to the new server.
Leo Miller
Leo
Nothing in life is ever so complicated that with a little work it can't be made more complicated.
July 1, 2010 at 11:30 pm
Thanks.
what we have 2000 environment and want to move all databases ( system and data ) to 2005 environment.
I know that data databases with detach and attach, but for system databases ( master and msdb ) was not sure as we need to also move all logins, permissions, rolls, DTS ,.. which are in master and msdb.
can I script msdb the same way as for master?
July 2, 2010 at 1:11 am
u can move the login from one instance to another by executing execi sp_help_revlogin SP, followed by the sp_hexidecimal SP.
it ll move all the login from one server to target server.
U can find enitre information regarding these two stored procedure on this article posted on this link..
http://support.microsoft.com/default.aspx?scid=kb;en-us;246133.
Hope this will help you
July 2, 2010 at 1:35 am
You can use the SQL Server Business Intelligence Studio to migrate the DTS packages. Create a new project, right-click SSIS Packages then "Migrate DTS 2000 Package".
Like the others, I suggest you do not bring over the MS2000 databases. Look up "What's New in SQL Server 2005" for the 1,001 items which in my opinion, will cause your server to crash if MS 2000 sys tables are forced unto it.
Viewing 9 posts - 1 through 8 (of 8 total)
You must be logged in to reply to this topic. Login to reply