Cirrus v4 didn't migrate my database

Yesterday I upgraded Cirrus to v4. We had been using an Access DB and that's no longer supported switched to SQL Server 2005. That's all great except that the installer didn't import any of the old DB info. All my SNMP strings were based on Custom Macros and Properties that didn't import. I opened a support ticket and was directed to the Microsoft SQL Server Migration Assistant which required the J# Redistributable Package and now wants me to go register for a license on some Microsoft page.

This is all leaving me very frustrated. I don't care what the database is but I do care that the installer didn't bring in all the data it should have and support just lobbed some tool at me and said "we don't support it but you can use this". I upgraded from the previous version to the latest one and the installer should either have brought over all my old data or thrown an error early in the install to say it couldn't do it and did I really want to proceed.

Can Solarwinds please supply a simple guide on getting on my old custom macros and properties into the new DB?

Find more posts tagged with

cirrus

unhappy

dissatisfied

migrate

Database

upgrade

Accepted answers

All comments

mark_wiggans

Sorry about the frustration- There needs to be a message stating the process including the registration with MS, which is required for the tool to work properly. I'll see if the issue you have with your custom macros can be addressed.

Did you have any luck with the MS SQL server Migration Assistant?

Haley

There are a couple of options for migrating your Cirrus Access database to SQL 2005 Express. One option is to use Microsoft's SQL Server Migration Assistant for Access, http://www.microsoft.com/downloads/details.aspx?FamilyId=D842F8B4-C914-4AC7-B2F3-D25FFF4E24FB&displaylang=en, which is most likely the tool recommended by support. This tool takes your Access database and easily migrates all information to a SQL 2005 Express database. As you stated, the J# Redistributable Package is required. Most customers have found that their server already had J# Redistributable installed on their machine. You can acquire the J# Redistributable from http://www.microsoft.com/downloads/details.aspx?familyid=F72C74B3-ED0E-4AF8-AE63-2F0E42501BE1&displaylang=en.

Another opton is to use the Upsizing Wizard within Microsoft Access. To run the Upsizing Wizard in Access 2000 or 2003, click on the Tools menu, point to Database Utilities, and then click Upsizing Wizard. You can find out more about the Upsizing Wizard at http://support.microsoft.com/default.aspx/kb/237980

Both options should retain all your information and preserve the defined indexes. If you continue to experience issues with the migration, please let me know.

DaveNoonan

I haven't registered SSMA yet and won't if it can be avoided.

I went looking in the Access DB and found the custom properties in the Nodes table. I was contemplating pulling the data and then writing SQL to get it into the new DB but I've had a new thought.

If I create the custom properties in the new install and then re-import the Nodes (possibly deleting everything from the new DB first) do we think it would import the custom properties? It's the properties (for 595 nodes) not the macros that I'm most concerned about.

Just to be clear my frustration is with the fact that the installer didn't handle this for me. It's a database migration. It should have been handled by the installer with just some basic input from me. If I had jumped three software versions I could understand that there wouldn't be a migration tool for that. I don't understand why Solarwinds just said "we don't support that one any more, good luck moving the data".

DaveNoonan

I created the custom properties in the new DB, deleted all the nodes and re-imported them. The custom properties imported correctly and at least that bit is okay.

Now I get to spend time figuring how to get my custom macros back.

I notice that Solarwinds is ignoring the question of why the installer left the customer hanging on the database conversion...

That may not be a question you can answer off hand but you could at least reassure me that you'll go back and smack someone on my behalf for not taking care of that.

mark_wiggans

I notice that Solarwinds is ignoring the question of why the installer left the customer hanging on the database conversion...
That may not be a question you can answer off hand but you could at least reassure me that you'll go back and smack someone on my behalf for not taking care of that.

Rest assured we hear you loud and clear and sorry I do not a have a better answer for you.

Haley

We appreciate your feedback. With the ease of use of the Microsoft Access to SQL 2005 Express migration tool, we decided to stick with their tool for migrating Cirrus databases from Access to SQL 2005 Express. We definitely understand your request and expectation for the installer to include a feature that migrates the database for you and for support to provide more assistance around the migration. Please feel free to email me directly if you are still experiencing issues.