Video Screencast Help
Search Video Help Close Back
to help
Not able to make it to Vision this year? Get a sampling in the Best of Vision on Demand group.

Migrating EV Databases to SQL 2k8 R2

Updated: 28 Jul 2011 | 1 comment
jasonwelch01's picture
0 0 Votes
Login to vote
This issue has been solved. See solution.

Hello

We're in the planning stage of migrating from SQL 2005 to a clustered SQL 2k8 and will be moving our EV SQL databases to this clustered SQL 2k8 pair...I just have 2 questions:

- i have the kb article explaining how to reconfigure EV to point to a different SQL server after moving the Databases to the new SQL server....Are there any gotchas, from EV perspective, when connecting to a clustered SQL2k8 R2 pair.  Are there additional configuration steps required to ensure EV knows about both instances of the cluster??

- prior to migrating any of the current SQL 2k5 EV databases to SQL 2k8 R2, are there any pre-migration steps/confguration that need to be run against any of the EV databases to ensure they'll successfully migrate to SQL 2k8??

Thanks

Discussion Filed Under:

Comments

SHI-CRO's picture
28
Jul
2011
0 Votes 0
Login to vote

EV doesn't need to know about

EV doesn't need to know about both instance of a cluster.  It will use the cluster server name like any other application that uses the SQL cluster.

If you're using this technote: http://www.symantec.com/business/support/index?pag..., you might be careful using the drop, copy and attach method.  I haven't experienced it personally, but I have heard of instances where a dropped database can't be re-attached to any SQL server for some reason.  A better method is to do a SQL backup (in the management studio) to a .bak file, copy the .bak file to the new server, and restore it to the new server.  Make sure to do the restore using the VSA credentials.

You don't need to do anything with the databases though when you move them to a new server, aside from making the changes detailed in the technote.