How To Move The Master(MSX) Server To A New Server(New Hardware)
Mar 11, 2008
I need information on steps to upgrade my current Master(MSX) server to a new server.
My MSX is a SQL 2K and it keep track of jobs in about 70 servers, some 2K and some 2K5.
I just notice that my MASTER database has some user tables and user SP ..and I am thinking to move them to 1 new user database but I am worried it will break something ..
What should I do ?
Moreover I wonder why Transaction log of MASTER can be full ( The recovery model is simple ) It should be fine , isn’t it?
We have an old machine which holds SQL server 2000 database. We need to migrate a whole database to a new machine which has SQL server 2005.
When we tried to move whole database using Import and Export Wizard, only tables can be selected to import/export. However we want to import/export the whole database, including tables, stored procedure, view, etc. Which tool should we use?
We have an old machine which holds SQL server 2000 database. We need to migrate a whole database to a new machine which has SQL server 2005.
When we tried to move whole database using Import and Export Wizard, only tables can be selected to import/export. However we want to import/export the whole database, including tables, stored procedure, view, etc. Which tool should we use?
Sql Server 7 Standard EditionMy Server was renamed and the normal steps of reinstallingand running sp_dropserver and sp_addserver were followed.Everything seems to work fine but jobs from the master server.I did defect the server as a target server since it appeared as offlineanyway.On trying to re establish the status of the server as a target serverFailed to make "serverName" a target serverEnlist into Master Server "MasterServerName" Failed(Error 14262)Your insight is appreciatedVincento
Can anyone refer me to good 'recipes' or sources of information on thistopic??I have Visual Studio Tools for Office, which installs SS 2005 Expresslocally to my XP box, and I want to develop in SS 2005, then copy thetables or queries or reports etc. to a SS 2005 Standard server.Thank you, Tom
We have a SQL Server 2000 ent edition sp4 with 3 small databases and one 4 GB database which is REPLICATED The Server has been bouncing like a yoyo today because of a disk controller problem and I am preparing to move the Instance to a whole new server this afternoon. The new Server will have the same IP and name as the original server.
Any suggestions for the easiest or most seamless way to make this happen? preferably using Backup and Restore since they plan on taking the old server down completely and then building a new server with the same name and IP ... any suggestions would be appreciated.
I moved the web app. I'm working on to another machine. Everything seemed to go well. Installed Reporting Services and configuration worked well with green ticks everywhere and I'm running reports in Report manager and in Visual Studio. However running off the web app. gives the message:
"The attempt to connect to Report Server failed" - there's also a ref. to an HTTP 404 error.
The install might not have gone as well as I thought because there was a "ReportServer" website created in IIS at same level as default. (Also Reports and ReportServer as virtual directories under Default website). The rogue website is 'stopped' at present. Would be grateful for any help with this. One thing is that I'm now behind a proxy so I'm using localhost:8080
I used aspnet_regsql to put membership tables, etc on sql server 2005. Is there a tool to help me build the web.config statement to point to these tables? I found the code below at http://www.c-sharpcorner.com/UploadFile/dsdaf/104092006022507AM/1.aspx?ArticleID=bc2ca2b0-9e3d-42ad-b4b9-0dce96231ce6 but it throws this error: Parser Error Message: Unrecognized configuration section membership. <membership> <providers> <remove name="AspNetSqlMembershipProvider" /> <add connectionStringName="MyDBConnectionString" enablePasswordRetrieval="false" enablePasswordReset="true" requiresQuestionAndAnswer="true" applicationName="/" requiresUniqueEmail="false" passwordFormat="Hashed" maxInvalidPasswordAttempts="5" minRequiredPasswordLength="7" minRequiredNonalphanumericCharacters="1" passwordAttemptWindow="10" passwordStrengthRegularExpression="" name="AspNetSqlMembershipProvider" type="System.Web.Security.SqlMembershipProvider, System.Web, Version=2.0.0.0, Culture=neutral, PublicKeyToken=b03f5f7f11d50a3a" /> </providers> </membership
We have 3 MSDE databases (3 seperate servers) which we need to make into one Sql 2000 server (new server). How is this done? Can't find anything clear about this.
Is this even possible? I tried to move an existing Sql Server Express .mdf file to SQL Server 2000 by copying the .mdf file to the server's folder and then tried to attach it. I get:
Error 602: Could not find row in sysindexes for database ID 9, object ID 1, index ID1. Run DBCC CHECKTABLE on sysindexes.
I realize that I'm moving back a version in SQL, however the structure of the database is very simple. Does anyone know?
Even if I can just script the thing to SQL 2000 would be helpful, however the .mdf is a file within my ASP.Net site, and does not show up in my Microsoft SQL Server Management Studio Express under the appropriate SERVERNAMESQLEXPRESS either, so I can't figure out how to script it out?
Hi guys, I have tried to use the sp_help_revlogin script to move logins from a sql 2000 server to a sql 2005 server. It works for users that have a password. But if the password is blank it will fail. Is there a work around for this since I can't change the users passwords? I have also tried SSIS package but that too doesn't work because of the same reason.
I'm looking for a way to list the target servers associated with a master server. The reason is that we're moving to another master server, and I'd prefer not to move the targets manually.
I've got most of the T-SQL already (sp_msx_enlist, sp_add_jobserver), but I'd like a scripted solution instead of a wizard.
I need to investigate about what happened to our production server at the last weekend.i restored it to another server which is development. I restored it under a name "old_master_2015_07_10".
But if I run a query
SELECT * FROM [old_master_2015_07_10].[sys].[servers]
it actually selects from master.sys.servers, not from my old_master... In order to prove it, I created a linked server in this, development server, and if I run SELECT * FROM [old_master_2015_07_10].[sys].[servers], it selects it. And in database selection drop-down box I also selected old_ master_ 2015_07_10. What I think it apparently recognizes familiar names like sys.servers and redirects the query to the master.
What I can do to select really from old_master_2015_07_10 database? I already thought about renaming sys.servers to something different, but did not do it not to break something in master in case if SQL Server will run it in master as well.
Hi,We are planning to create a prod environment on our Dev server, bycreating a new named instance on DEV. Our prod server is running onsql enterprise edition 64bit and dev on SQl enterprise 32bit.Could we copy all the databases from prod server includingMaster,msdb,model onto our dev server, and bring up all the databases?Does Master store information about the version of SQl server?Thanks for your helpGG
I have never done this in a DR scenario before. What I used to do in SQL Server 2000 was apply the logins to a new installation of SQL 2000 then recover the application databases. I'm using 2005 now and I'm in a different mode where I would like to be able to recover the system (master, model, msdb) to a different server with the same SQL Server 2005 build ---- 9.0.3054. I'm following the procedures from Microsoft where they state to place the instance in single user mode first then invoke SQLCMD then perform the restore. Sounds simple enough. C:> SQLCMD > RESTORE DATABASE MASTER from DISK = 'Z:MINIDRmaster_backup_200804200315.bak'
The console is coming back with a message that the backup set holds a backup other than the existing master database. So I suppose that this cannot be done and is only intended for recovery on the same instance.
how can we manage the db transfer when we are upgrading from 2000 to 2005? what is the right way to do that? where can we find something to read about it?
Hi all, To move SQL server on SRV1 to SRV2, I use following steps: 1. Detach all my user-databases on SRV1 2. Stop SQL Server on SRV1, SRV2 3. Copy all my user-databases files on SRV1 to SRV2 4. Copy MASTER files on SRV1 overwrite to MASTER files on SRV2 5. Restart SQL on SRV2 6. Attach all my user-databases o SRV2 then when I use SELECT @@SERVERNAME on SRV2, I get result SRV1. Which the best way to update system with right server name? Thanks for any help, PTH
I have several jobs (most scripted in activeX) that I need to move to a different server. Is there an easy way to "copy and paste" them from one server to the other? (SQL7 to SQL2k)
I have a db that I created on my local machine and need to move it to our server. The problem is that I created it with sql server 2005 express and our server is a sql server 2000 so restore and attach don't work. I don't have management studio (just express) so I don't know what I need to do to move it. Any help is appreciated.
Our company develop software based on SQL7 . ”DBA” position is really a developing (creation of triggers, stored procedure …) Could you give an advice from you personal experience what task should I practice in order to be ready for real DBA job and how YOU moved from developer to DBA
I am fairly new to SQL Server 7. I have a SQL server database on one machine (box A). Now I installed a new box with SQL server on it (box B). How do I move the database from box A to box B?
What are the steps involved? What is the easiest way to do it? What files need to be copied over?
Hi, all. I have more than 100 DTS packages on one server which need to be migrated to another new server. What's the easiest way to do it? I can do it by opening each package then using save as to save into another server. But I have more than 100, so it is kind of tedious to do it.
Is there a way like export those packages then import them? Or script them then run it? If yes, Let me know how.
We are currently moving our environment. I was told that we need to copy all the stuff over. More specifically, we want to move everything except the data, as our data is dynamic and will fill up in a few days by itself.
What is the best way to move everything over from one server instance to another?
My current approach is the following:
1. Create the file groups we have on our current server on the new server 2. Script out all databases with stored procedures, functions, views, priviliges, indexes ... 3. Script out all the jobs 4. Script out all the dts packages (or rather save each in a file) 5. Load all scripts into the new sql server 6. Re-create user accounts (can these be scripted out also and then loaded?)
Am I missing something or is there a wiser alternative?