casafrog007 - Friday, June 22, 2007 11:29 AM:
Hey all - I have Innovator running in a test setup (2K3 SBS Server, SQL Exp 2005) and have decided it can now move over to production, which of course is on a different box. The test setup of course has active data in it that we wish to retain. Though not a SQL guru, I have kept my head above water sufficiently with other SQL installs (Great Plains, Accounting Pro, etc) and have migrated those tables fine between machines before. My typical method is to replicate a blank instance on the target machine, stop all services, then copy the active Sql SBD/SBL files over, then restarting services. Are there any other config files that are kept by Innovator that would not allow this approach? As noted, I'm not just copying 2 files blindly, they are going into a fresh Innovator target with a duplicate-defined IIS/.Net/Sql setup, just blank, so all the login hooks, pages, DSN's etc will be existent.
The vault will be the same absolute path as well, since I built it as a network mapped drive.
The target will likely be an XP Pro machine with Sql Express 2005. Same rev SQL, same rev .NET....(just a change in the OS)
Thanks,
Ted.
Bill - Friday, June 22, 2007 12:27 PM:
Hi Ted,
Well, this is actually pretty simple, but let me ask a few questions:
1) Is the production machine already in use, or are you installing it for the first time in production? If this is the first time, why not back up the test database, and restore it to the production server? (No risk of missing any required table data that way.)
2) Did you make any customization in the test code tree? (Adding images, htmls, or enabling single sign-on, etc.)
3) I'm not sure I read that right, is your production server a Windows XP machine, or was that the vault server?
Basically, if you are installing the new production instance I can outline a high level plan. First, I would install Innovator on the production server, with the configure only option for the database. Then, I would restore the database from the backup. Next I would copy any custom files into the production code tree. Finally test any custom pages to make sure they load properly.
-Bill
casafrog007 - Friday, June 22, 2007 5:46 PM:
Bill -
The production machine hasn't been used yet, so there isn't any need to "supplement" or merge data - strictly overwrite. I didn't see a backup/restore function built into Innovator. Are you meaning using a 3rd party database backup piece? (This will also show that I know just enough SQL to be dangerous, but often not helpful... I typically am a creature of habit, so...copying typically two files is what I've always done in the past.) I won't ask you to teach me SQL, but is there a method you prefer to recommend instead?
The PLM module has been added, custom workflows and user data added, and of course, parts and projects.
I have changed out some high-level logos, but that's no big deal to copy over. My main concern was if there were lots of little hidden config or xml files.
And yes, the production Innovator server will be running XP pro. I have a similar box running MS Accounting Pro and Sql-Exp 2005 in a server configuration with about 7 concurrent fulltime connections, and XP doesn't seem to be slowing anything down. We unfortunately have a Server SBS installation on the network, which precludes any other Windows Server installations. I've tried it before, and SBS will always command over the other installs and shut them down, regardless of the install type or services offered (MS verified). I can't move the SBS server for a little while yet due to a lot of custom programming and some legacy software that we don't have sources for anymore.
Thanks,
Ted.
Bill - Friday, June 22, 2007 6:23 PM:
Actually, I'm not proposing any third party tools. Just use standard SQL Server backup functionality. You can then restore from that backup to the new server. This is definately your easiest option.
I will try to get the manual process written up for the forum over the weekend.
If you didn't change any manual config files, then I wouldn't bother with copying any of them. Just copy the custom files (like logos) to the new install instance on the new server.
Running server apps on Windows XP is something you have experience with, so I will trust your judgment on it. Just keep in mind, Windows XP is really only meant for development with Innovator. It is hard to say what performance differences you will see in production.
-Bill
