Migrating from MSDE to MSSQL and upgrading?

[Terry Auspitz]

Greetings,

I am currently running HPSIM 4.2 on Windows 2000, with the database running on the same box via MSDE. We've outgrown this configuration (the server is managing 853 devices) and would like to migrate the database to MSSQL. We're also planning to upgrade to the latest version of SIM, and move SIM to a new physical server.

When this project is complete, our goal is to end up with the following:

- HPSIM on a new physical server.
- Running SIM 5.0 SP5 on Win2K3
- SIM database on a separate MSSQL server.

Can anyone offer suggestions on how to best accomplish this? I want to make sure I don't unnecessarily duplicate steps, and that I don't lose access to my data.

Thanks,
~Terry

[Rob Buxton]

I'd consider starting from scratch with a new database.
You can leave the old database intact and access it via standard SQL tools to get what data you require.

I'd also consider waiting to HPSIM 5.1 and see what the overall forum view of that is - e.g. number of issues raised.

Other steps can depend on how you set up trusts, e.g. if Trust by certificate then that will need to be updated on all servers. You can do it by updating the SMH and redeploying.

You'll also need to change the VCA configuration if the VCRM is also moving. Most likely it is.

[Terry Auspitz]

Thanks Rob.

I'd really prefer not to move to a new database if at all possible. First, none of us in our NOC are trained as SQL administrators. I can get by in a pinch, but I hate to have things too dependent on one person, plus there's the fact that after we move SIM to the new server, we'll be decommissioning the old one. I don't know of a way to perform SQL queries on a box that no longer exists. ;-)

Also, since the existing database is MSDE, I believe it's not possible to hit that database remotely anyway.

~Terry

[Rob Buxton]

Terry,
On the last point, I had until recently an MSDE database from one of my earliest HPSIM installs running on my workstation. It was easily accessible. I don't think it was too difficult to maintain.

What data are you trying to retain?
Were you running a Historical Data collection task?

There's a reasonably good guide around of how to update from HPSIM 4, it does take a few jumps though, I don't think you can go directly to HPSIM 5.0 SP5.

[Terry Auspitz]

Rob,

The key is that you had the MSDE database running on your local workstation. That's not really an option for me - first because I'm not the only person who will need access, and second because my workstation is a laptop, and taking that information out the door would be a security policy violation.

I'm trying to retain the full alert history for all our monitored devices. We use this to detect trends and potential issues with our hardware. Losing that data would not be fatal, but it's something we definitely want to avoid.

I'm sure it's possible to move the data from MSDE to SQL -- what I need is a pointer to something that can tell me how to do it, and a recommendation as to whether I should do it before or after upgrading to version 5. Starting from scratch with a fresh install is easy, and if I wanted to do that, I wouldn't need to post here first. ;-)

I'm fine with intermediate steps if I need to take them.

~Terry

[Rob Buxton]

The MSDE stuff was originally on a server, I moved it to my workstation but I don't have the details as to how I did that. I no longer have MSDE installed at all so I cannot verify it. I've a feeling it's now attached quite happily to our SQL Server and available for really old lookups.

I do have access to SQL Server expertise here, so things are a bit different.

There are a number of items available around that detail how to migrate an MSDE database to the new SQL Server 2005 Express or the older SQLServer 2000.

But to achieve what you want and preserve the data I'm not sure of which to move/upgrade first.
But I'd look to try and copy the MSDE Database to a SQL Server and attach it and see if I could at least access it separately from HPSIM before I did anything. Given a suitable name it could at least be retained no matter what.