Video Screencast Help

EV SQL database movement

Created: 18 May 2009 • Updated: 21 May 2010 | 3 comments

Hi --

we have Enterprise vault 7.5 SP3 with local SQL 2000 server Database. In order to consolidate SQL servers we plan to move database from local SQL server to remote SQL server (2005).
how do i proceed SQL database movement.

Thanks in Advance

Sridhar

Comments 3 CommentsJump to latest comment

Nicola Rositani's picture

See Document ID 273272 at http://support.veritas.com/docs/273272.

I do the same 1 years ago and I don't have any issue.

Regards
Nicola

Nicola Rositani's picture

If you think this solution is ok, don't forget to vote it and mark it as solved

Thanks

Paul Grimshaw's picture

As you are moving from a SQL 2000 to a SQl 2005 server then there are a few other things that need to be done as the technote referenced refers to moving databases from one SQL server to another that is the same version.
In a previous life I assisted a few customers in their upgrade to SQL 2005 and generally sent them the following information and I have had a 100% success rate with it so this will be a good starting point:-

Technotes around SQL 2005:-

http://support.veritas.com/docs/287521
http://support.veritas.com/docs/281261
http://support.veritas.com/docs/293852
http://support.veritas.com/docs/293475

1. If your SQL server is clustered then make sure that the VSA is a local administrator on all nodes of the cluster

2. Ensure that you create a SQL login for the VSA and that this has at least db_datareader role assigned to all vault related databases. It also needs the db_creator role for when you need to create databases in the future.

3. What is VERY important is that the SQL 2005 server that you are going to has the same server collation than the SQL server you are coming from. Also check that all of the system databases have the same collation. If not then you will have problems when upgrading next. This is the last technote referenced above.

4. Also when you move the databases ensure the ODBC DSN points to the new SQL server

5. Lastly when you have moved the databases ensure that the compatibility level of your SQL databases are at 90 not 80. This is on the properties of each database in the options section

EV Backline Technical Support Engineer APJ Region