steps to attach and dettach the db from sql 2005 to sql 2008 on same server

27
STEPS TO ATTACH AND DETTACH THE DB FROM SQL 2005 TO SQL 2008 ON SAME SERVER. From my test machine, I have EPO 4.6.5 running with sql 2005 Expess version ( 9.0.0.4035) SQl 2005 SP3.

Upload: mishur18

Post on 12-Dec-2015

237 views

Category:

Documents


8 download

DESCRIPTION

okejs

TRANSCRIPT

Page 1: Steps to Attach and Dettach the Db From SQL 2005 to SQL 2008 on Same Server

STEPS TO ATTACH AND DETTACH THE DB FROM SQL 2005 TO SQL 2008 ON SAME SERVER.

From my test machine, I have EPO 4.6.5 running with sql 2005 Expess version ( 9.0.0.4035) SQl 2005 SP3.

Page 2: Steps to Attach and Dettach the Db From SQL 2005 to SQL 2008 on Same Server
Page 3: Steps to Attach and Dettach the Db From SQL 2005 to SQL 2008 on Same Server

NOTE: Need to remove the dependencies of the existing SQL services with epo services, as steps CAUTION: This article contains information about opening or modifying the registry.

The following information is intended for System Administrators. Registry modifications are irreversible and could cause system failure if done incorrectly.

Before proceeding, McAfee strongly recommends backing up your registry and understanding the restore process. For more information, see: http://support.microsoft.com/kb/256986.

Do not run a .REG file that is not confirmed to be a genuine registry import file.

1. Click Start, Run, type regedit and click OK.2. Go to [HKLMSystemCurrent ControlSetServicesMCAFEEEVENTPARERSRV].3. Right-click DependOnService and select Delete.4. Go to [HKLMSystemCurrent ControlSetServicesMCAFEEAPACHESRV]. 5. Right-click DependOnService and select Delete. 6. Go to [HKLMSystemCurrent ControlSetServicesMCAFEETOMCATSRV200]. 7. Right-click DependOnService and select Delete. 8. Restart the computer.

The above information available in the KB68427. http://kc.mcafee.com/corporate/index?page=content&id=KB68427

Page 4: Steps to Attach and Dettach the Db From SQL 2005 to SQL 2008 on Same Server

Fresh Installing the SQL 2008 R2 SP1

Express from server running with SQL 2005 Express version.

Note: SQL can be installed multiple versions on same server.

Page 5: Steps to Attach and Dettach the Db From SQL 2005 to SQL 2008 on Same Server

The above screenshot is for the SQL 2008 R2 SP1 64bit installation, so you can see the path: C:\Program Files\Microsoft SQL Server\

Whereas the Previous sql 2005 Express is 32bit and path: C:\Program Files (x86)\Microsoft SQL Server\MSSQL.2\MSSQL\Data

So, The new installation will be pointing to different path and only few components related to 32bit will be installed on the default path: C:\Program Files (x86)\Microsoft SQL Server.

Note: If still have any concerns, you can change the path, which helps confusion, while attaching the DB from 2005 to 2008. More information will be avail in coming slides.

Page 6: Steps to Attach and Dettach the Db From SQL 2005 to SQL 2008 on Same Server

The above snapshot is very important, as you can it ask for the instance name, I given custom name as “EPO2008”.

It specifies the new instance location as: C:\Program Files\Microsoft SQL Server\

Sql Server directory path: C:\Program Files\Microsoft SQL Server\MSSQL10_50.EPO2008

The snapshot clearly tells still folder: MSSQL10_50.EPO2008 is not created, and it will only after configuring the instance name and path.

Above screenshot, shows the other instance names, Path and versions avail on this server.

Page 7: Steps to Attach and Dettach the Db From SQL 2005 to SQL 2008 on Same Server

The above snapshot is for the credentials, you can leave as DEFAULT or click on use the same account button and add the administrator and password.

I suggest, to leave with defaults. Since next screen it will pick the administrator credentials.

Page 8: Steps to Attach and Dettach the Db From SQL 2005 to SQL 2008 on Same Server

Here, If you are created the SQL user specify OR leave with windows credentials and then install the SQL management studio 2008 for 64bit and connect with instance (my ex:EPO2008) and then create the sql user and update core/config

To download the SQL Management studio 2008 Express

http://www.microsoft.com/en-us/download/details.aspx?id=22985

Page 9: Steps to Attach and Dettach the Db From SQL 2005 to SQL 2008 on Same Server
Page 10: Steps to Attach and Dettach the Db From SQL 2005 to SQL 2008 on Same Server

The above snapshot, with path of the epodb from sql 2005 ( EPOSERVER Instance) and new path of SQL 2008 installed, without the epo db.

Page 11: Steps to Attach and Dettach the Db From SQL 2005 to SQL 2008 on Same Server

NOTE: Before Dettaching, please stop the EPO Services

Page 12: Steps to Attach and Dettach the Db From SQL 2005 to SQL 2008 on Same Server
Page 13: Steps to Attach and Dettach the Db From SQL 2005 to SQL 2008 on Same Server

After dettaching, the EPO DB will be removed from the list, but you can see the MDF and LDF file available from same location.

Page 14: Steps to Attach and Dettach the Db From SQL 2005 to SQL 2008 on Same Server

Manually copied the MDF and LDF file to SQL 2008 location.

Page 15: Steps to Attach and Dettach the Db From SQL 2005 to SQL 2008 on Same Server

Now, disconnect and try to reconnect with the specified instance name: [EPO2008 from my example]

Connected with MASTER ( Default DB), Right click on DATABASES- Select: ATTACH as below

Page 16: Steps to Attach and Dettach the Db From SQL 2005 to SQL 2008 on Same Server

Note: I have manually copied the MDF files to new location, beacause the default path is the same, so it will pointing to this MDF file easily.

Page 17: Steps to Attach and Dettach the Db From SQL 2005 to SQL 2008 on Same Server

The snapshot below, shows the status of the EPO DB is reporting to which Instance, and based on the instace and SQL build number, we come to know it is sql 2008 and managed by EPO2008 Instance.

Page 18: Steps to Attach and Dettach the Db From SQL 2005 to SQL 2008 on Same Server

The next step to update these changes to Core/config, which helps to connect the EPO console from the new instance.

Note: From the core/config page, it is not required to specify the instance name, the db connects with the Port number, and every instance have different ports, from the SQL configuration manager, you can see all the instances and it’s properties.

Once you check the TCP/IP protocol for EPO2008 Instance, and you can update the same port in the core/config and if needed with sql authentication or with default windows authentication.

NOTE: Check the snapshot as below, I have opened the SQL configuration manager from sql 2005 and 2008, By default the TCP/IP is disabled from the

Page 19: Steps to Attach and Dettach the Db From SQL 2005 to SQL 2008 on Same Server

SQL2008, and only listing with 2008 Instance. Please enable the tcp/ip, Name Pipes and restart the SQl EPO2008 service.

After restarting the SQL service for EPO2008 instance, you can see the TCP port visible.

>> Now, you need to start only EPO application server service, and other two services will won’t start, because the DB pointing earlier is dettached.

Page 20: Steps to Attach and Dettach the Db From SQL 2005 to SQL 2008 on Same Server

So, Presently you can’t login to

https://<EPO IP>:8443/core/orionSplashScreen.do

But, You can login with https://localhost:8443/core/config and see the snapshot the core/config is reflecting with old data, so I will remove the instance name and then update new port (49305 as my example).

Creating the new sql user from sql management studio, by logging in with EPO2008 Instance.

>> Right click on SQL server 10.50.2500 – properties –s ecurity tab – check it is mixed mode, if not select SQL and Windows and Mandatory to restart the sql services and login in again.

Page 21: Steps to Attach and Dettach the Db From SQL 2005 to SQL 2008 on Same Server
Page 22: Steps to Attach and Dettach the Db From SQL 2005 to SQL 2008 on Same Server
Page 23: Steps to Attach and Dettach the Db From SQL 2005 to SQL 2008 on Same Server
Page 24: Steps to Attach and Dettach the Db From SQL 2005 to SQL 2008 on Same Server

After creating the User ( ex:EPOSA), updating the information in core/config and testing the connection. If it is successful, Apply and restart the EPO services.

NOTE: Please take the backup of DB.properties, before making any changes from core/config, This is Recommended.

Default Path: C:\Program Files (x86)\Mcafee\ePolicy Orchestrator\Server\conf\orion ( copy file db.properties to another location).

Page 25: Steps to Attach and Dettach the Db From SQL 2005 to SQL 2008 on Same Server
Page 26: Steps to Attach and Dettach the Db From SQL 2005 to SQL 2008 on Same Server

You can see Date Modified is updated to new DB located in sql 2008 folder.