Moving IssueView from
One SQL Server to another
(or from 2000 to 2005)
The easiest way to move an IssueView database from one SQL Server to
another is to perform a backup on the existing server, then restore the backup
on the new server. This procedure can also be used to upgrade your database
from SQL Server 2000 (or SQL Server 7.0, or MSDE) to SQL Server 2005.
Because IssueView uses some SQL Server login IDs, it is necessary to use an
IssueView utility to perform the Restore.
On The SQL Server:
-
Launch the IssueView Win32 client, and login as 'admin'
-
Select 'Backup Database' from the Tools menu.
-
In the Save File dialog, select a location for the backup file, and supply a
name. Please note that while the browse dialog is displaying the local machine,
the backup file will be created on the SQL Server . It is best to
create the backup in the root of the C: drive.
-
Copy the backup file from the old SQL Server to the new one.
-
On the new SQL Server, download RestoreBackup.exe from our web site:
http://www.IssueView.Com/RestoreBackup.exe
-
Run RestoreBackup on the new SQL Server. If you get an error complaining
"class not found", it means that the Microsoft JVM is not installed on the SQL
Server. You can download the installer from
http://www.IssueView.Com/msjavx86.exe. Install the JVM, then
restart RestoreBackup.
-
In the first screen you must supply login credentials on the new SQL
Server. If you're logged in with a Windows ID that is part of the
Administrators group you can use 'Windows Authentication'.
-
On the second screen, select the backup file which you created in step 3.
-
On the third screen, click 'Finish' to begin the restoral process. An average
database takes less than 30 seconds. A medium sized database (e.g. 100MB) can
take several minutes.
After the restore completes, if you are unable to log on to the new
server, make sure the new server supports SQL Server login IDs, and
Port 1433 is open on the Firewall. More information can be found
in our FAQ
On each IssueView Client Machine:
Each IssueView client that used the original IssueView database, on
the Source Server, will need to update their configuration to point to the
database on the Destination Server.
In the login dialog, there is a browse button '...' next to the
Database dropdown. Click the '...' button and enter the connection info for the
Destination SQL Server. Normally you need only update the Database (SQL Server)
name.
IssueView connection information is stored in each user's
Registry. As an alternative, you could create a .reg file to update each
user's Registry. You would have to have each user execute the file (and
authorize the update to the Registry), or push the update out to affected
machines via a Windows Login Script.
Here is an example .reg file:
REGEDIT4
[HKEY_CURRENT_USER\Software\IssueView\UI]
"DefaultDb"="ISSUEVIEW (SQL Server)"
[HKEY_CURRENT_USER\Software\IssueView\UI\Databases]
[HKEY_CURRENT_USER\Software\IssueView\UI\Databases\0]
"Name"="ISSUEVIEW (SQL Server)"
"Database"="SQLSVR02"
"Type"="2"
Note that the value for DefaultDb and Name match.
You will be editing the value in "Database". Replace SQLSVR02
(or rather whatever the name of your orgininal server was) with the
new SQL Server name. If the new Server has an Instance Name, replace
SQLSVR02 with ServerName\InstanceName.
Save your changes to a file named 'IssueView.reg'. When your
users doubleClick on the file they'll be prompted, "Are you sure you want to
add the information in IssueView.reg to the Registry?" They must click
'Yes' to update their settings.
IssueView-Web, WebSupport, and IvMonitor
All three additional interfaces will need to be updated so they'll
know where to find the new database. The simplest way to update them is
to un-install each interface, then re-install it. During the install
you'll be prompted to enter the Database location. The installer will
also configure each application to use the correct password.
If you are unable to perform an UnInstall/ReInstall, you can edit
web.config manually to reflect the new database location. But you'll need
to manually set the password for the SQL Server Login ID IM_Web, and
enter the password into web.config as the value for IVWeb. The
IvMonitorAdminWizard will allow you to enter these values for IvMonitor.
|
