Moving from SQL express to SQL server

When I installed my trial versions of NPM, NCM, NTM and SAM I used the default local SQL express for the install. Now that I have purchased these products I would like to use our database server.

Is it possible to move my databases from the local express edition to our SQL server 2005 edition?

How do I do this?

Find more posts tagged with

sql_express

Accepted answers

jangliss

According to the docs, it's a case of backup, move, restore, and re-run the configuration tool.

http://www.solarwinds.com/documentation/Orion/docs/MovingYourOrionNPMDatabase.pdf

SolarWinds Tutorial - Orion 8.1 Database Migration

Good luck!

All comments

jangliss

According to the docs, it's a case of backup, move, restore, and re-run the configuration tool.

http://www.solarwinds.com/documentation/Orion/docs/MovingYourOrionNPMDatabase.pdf

SolarWinds Tutorial - Orion 8.1 Database Migration

Good luck!

mrxinu

Exactly right, but beware - oddly enough the NPM services have that SQL express as a dependency. So go ahead and go through the motions but DO NOT uninstall SQL express. Just turn it down and leave it there.

Aforsythe

You should be able to add the databases in your full version and browse to the existing MDF and LDF files.

In your MSSQL Server Management Studio, right-click on Databases and choose "Attach" instead of "New Database"

I'm not sure about Steven's reply though, as I beleive the Express service needs to be stopped and disabled for you to move the databases. If you need that service as a dependancy, then you will need to COPY the databases (both the MDFs and LDFs but not any of your system DBS) to your desired new location (By Default it would be \MSSQL\Data) And then attach the new copies. That will leave SQL Express intact and functioning while your new Copies will be running under the full version.

carlosl.ramirez

Hi, can you explain how I can turn it down SQL Express? I recently have done the migration to a separate SQL Server, however my polling server still has high RAM (12GB) consumption, despite the DB is now on a separate Server.