MS SQL 2000 Server with CDR DICOM 3.5 and Recommended WAN Configuration

Transcription

1 This document describes the steps for users installing CDR DICOM 3.5 in a Multi-Office Wan Environment, who meet one of the requirements below: Existing users of CDR DICOM with a Full MS SQL 2000 Server DICOM database. Existing users of CDR 2.6 upgrading to CDR DICOM 3.5 and converting to a Full MS SQL 2000 Server DICOM database. New users implementing CDR DICOM 3.5 with a Full MS SQL 2000 Server DICOM database. Recommemded WAN for DICOM 3.5: The Main Office will house a Full Mircrosoft SQL 2000 Server(CDR DICOM 3.5 is shipped with an MSDE SQL Server). The MSDE has a 10 concurrent user limit and a Full Microsoft SQL 2000 SERVER will need to be purchased for configurations with more than 10 users. This server will hold the DICOM patient database for all offices and have pointers to the UNC volume paths for each local image Server(see next item for local server explanation). Each office will have a local file server for image storage. Each Server will be setup with a shared images folder with Full Control for all users. These Server s will be accessible across the WAN through a UNC path. Pulling images across a T1 will be slow, that is why we recommend the local image servers. Images will only be pulled across the T1 when a patients images are located at a different office.most images will be accessed locally. The Client systems will be connected to the Central SQL Server and have their default image path pointing to their local image server through the CDR DICOM Client software (example image path: \\Office1\images\). They will also have access to all image Server s on the WAN via the each offices UNC path. The Central SQL Database will have a UNC volume path for all local image servers. The following steps describe how to configure the Full SQL 2000 Server for DICOM.

2 STEP 1: To be completed by all users listed above Installing MS SQL Server 2000 as a named Instance In order to install CDR Dicom for Windows 3.5 on a server running MS SQL Server, it is necessary to first prepare the server by installing a named instance of MS SQL 2000 on the server machine. The Instance Name, Database Name, and SA password all need to be identical to those listed within this document in order for the installation to succeed. Figure 1 To begin the installation, you will need to start your MS SQL Server 2000 installation on the local server, which is running your prior version of MS SQL Server. Verify that the name listed for the server is correct, and then click on Next to continue.

3 Figure 2 On the Installation Selection screen (figure 2), verify that the option for Create a new instance of SQL Server, or install Client Tools is selected, then click on Next to continue. Figure 3 When prompted for an Instance Name (figure 3), type in CDRDICOM, then click on Next to continue.

4 Figure 4 On the Services Accounts screen (Figure 4), use the same service settings used during the original MS SQL 2000 installation, then click on Next to continue. Figure 5 On the Authentication Mode screen (Figure 5), we will choose Mixed Mode authentication. At this point it will ask you to enter and confirm a password for the sa login of this instance. You must choose cdr as the password for the sa login.

5 Figure 6 Under Licensing Mode, please select the appropriate licensing mode and number of licenses. Figure 7 Near the end of the installation procedure (figure 7), you may get a warning message stating that Setup needs to shutdown certain tasks in order to proceed. Click on Next and complete the installation.

6 STEP 2: Only to be completed by existing users of CDR DICOM with an existing MS SQL 2000 Server DICOM database. All other users proceed to Step 3. Using SQL DTS to import data from a CDR Dicom For Windows 3.01 installation to a CDR DFW 3.5 Named instance installation. Please note that these instructions assume the following: 1. CDR DFW 3.01 has been in operation prior to this install, using MS SQL server for storing patient data. 2. A named instance of SQL server using the CDRDICOM name has been installed on the computer running MS SQL server. 3. CDR 3.5 was not previously installed. 4. You are logged in using an account which has administrator security access

7 Begin by verifying the existence of the CDRDICOM named instance. Highlight the named instance, open the DTS import wizard by selecting TOOLS->WIZARDS from the menu.

8 Make certain that you select the DTS Import Wizard as opposed to the Export Wizard, then click on OK to continue.

9 On the first screen of the DTS Import Wizard you will be asked to specify a Data Source, Server, and Database to import your data from. Under the Data Source drop down menu, select the Microsoft OLE DB Provider for SQLServer. For Server, select either (local) or the name of your MS SQL server. (Do not select the named instance (CDRDICOM) at this point, as the named instance will be the destination of your import, not the source). Below Server you will be able to choose the method by which you wish to connect to the MS SQL Server. In the above example, we have Use Windows Authentication selected. Under Database: select the name of the database which has your CDR DFW 3.01 data. In the above example, we are using the DICOM database as our data source. Once these selections have been made, click on Next to continue.

10 This is the DTS Import Wizard data destination screen. For the Destination: drop down menu, we will be selecting Microsoft OLE DB Provider for SQL Server. Under the Server drop down menu, you will need to find the Named Instance of MS SQL Server which you installed earlier. This Named Instance will appear on the list as SERVERNAME\CDRDICOM. In the above example, our server name is MYSERVER, and as a result we have selected MYSERVER\CDRDICOM. Next we will select the authentication type we wish to use to connect to this Named Instance. During the installation of the Named Instance, we created an SA account with a default password of CDR. Please select Use SQL Server Authentication and use the Username: SA and Password: CDR.. For Database: you should select <new> from the dropdown menu.

11 After selecting <new>, the Create Database screen will appear. For the database name type in CDRData. Please note that this needs to be typed in exactly as listed above in order for CDR Dicom For Windows 3.5 to function properly. The values listed for initial Data File Size: and Log File Size: can be left at their defaults, as they will grow automatically as the MS SQL server needs the additional space. Click on OK on the Create Database screen, then on Next > to continue.

12 The Specify Table Copy or Query screen is where we tell the DTS Import Wizard how we wish to select data to import. Please select the third choice, Copy objects and data between SQL Server Databases, then click on Next > to continue.

13 On the Select Objects to Copy screen please make sure that the following choices are selected: Create Destination Objects Drop Destination objects first Include all dependent objects Copy data Copy all objects Use default options Once these have been selected, click on Next > to continue.

14 The final screen of the DTS Import Wizard is where you will select when you wish to run this package and whether or not you wish to save this package for future use. Verify that the only option selected is Run immediately then click on Next > to complete the DTS Import Wizard and have the DTS package execute, thereby copying importing your CDR 3.01 data into the new named instance of MS SQL server.

15 STEP 3: To be completed by all users Installing CDR DFW 3.5 Server in a MS SQL 2000 Environment The instructions listed in this document assume that you have already performed the following steps: 1. Installed MS SQL Server as a Named Instance. 2. Using the MS SQL Server DTS Import Wizard, copied all CDR SQL data from your old database to the CDRData database residing in the new Named Instance install of MS SQL Server (For existing DICOM users)

16 Begin by inserting your CDR Dicom For Windows 3.5 CD, and choosing a Server installation.

17 During the installation procedure you may receive the message shown above. This message appears when the install detects an older version of your CDR SQL database. We will address this issue after the CDR DFW 3.5 server software has completed installation.

18 During the installation process, please verify that the server software is pointing to the correct machine during install. If the server name does not match that of the server housing your data, please contact Schick Technologies, Inc. or the Patterson Technology Center for additional assistance.

19 After the installation process has completed, you will need to execute the DBUpdate utility. This utility can be found under your CDR Dicom Shared Files folder. (In a default installation, the Shared Files folder is located under C:\Program Files\Schick Technologies\). From within this folder, find and execute the DBUpdate utility by double clicking on it. This utility will connect to your MS SQL Named Instance and modify your CDR DFW 3.01 tables to match the new CDR DFW 3.5 data definitions.

20 STEP 4: To be completed by all users Modifying or verifying the Volume table in CDR DFW 3.5 The purpose of this document is to instruct the user in how to modify or verify the Volumes table in CDR DFW 3.5. The volume table must accurately reflect the changes made when updating from CDR DFW 3.01 to CDR DFW 3.5. If upgrading from CDR 2.6 the volume table should be verified to reflect the correct image path. Through the CDR Data Administration Utility, go to Tools->Show Volumes. Listed on this screen will be the current Default Volume location, as well as any existing Image volumes. Please verify that the Default volume is listed as a network share via a UNC Path. If this is not the case, please contact Schick Technologies, Inc. or the Patterson Technology Center for assistance. Highlight the old CDR DFW 3.01 Images volume (C:\Images\ in the above screen shot), then click on Modify Volume.

21 In the Modify Volume screen, you will click on the Browse button and select the network share which houses your images. This share is created as part of the CDR DFW 3.5 Server software installation. Under standard installs, this share will be listed as your Default Volume. In the above example, this share is named Images and is located under the computer named Myserver. Once you have selected this share, click on OK in order to proceed.

22 Verify that the path name listed within the Volumes window is correct, and that it is listed images. If you have multiple volumes then verify the default volume is correct. You can now continue with the CDR DFW 3.5 installation, installing the software on your workstations normally.