MS SQL 2000 Server with
CDR DICOM 3.5 and
Recommended WAN
Configuration
c r e a t i n g t h e i m a g e T h i s d o c u m e n t d e s c r i b e s t h e s t e p s f o r u s e r s i n s t a l l i n g C D R D I C O M 3 . 5 i n a M u l t i - O f f i c e W a n E n v i r o n m e n t , w h o m e e t o n e o f t h e r e q u i r e m e n t s b e l o w : • E x i s t i n g u s e r s o f C D R D I C O M 3 . 0 . 1 w i t h a F u l l M S S Q L 2 0 0 0 S e r v e r D I C O M d a t a b a s e . • E x i s t i n g u s e r s o f C D R 2 . 6 u p g r a d i n g t o C D R D I C O M 3 . 5 a n d c o n v e r t i n g t o a F u l l M S S Q L 2 0 0 0 S e r v e r D I C O M d a t a b a s e . • N e w u s e r s i m p l e m e n t i n g C D R D I C O M 3 . 5 w i t h a F u l l M S S Q L 2 0 0 0 S e r v e r D I C O M d a t a b a s e .Recommemded WAN Configuration 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.
MS SQL 2000 Server with
CDR DICOM 3.5 and
Recommended WAN
Configuration
c r e a t i n g t h e i m a g eSTEP 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
MS SQL 2000 Server with
CDR DICOM 3.5 and
Recommended WAN
Configuration
c r e a t i n g t h e i m a g e Figure 2On 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
MS SQL 2000 Server with
CDR DICOM 3.5 and
Recommended WAN
Configuration
c r e a t i n g t h e i m a g e Figure 4On 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
MS SQL 2000 Server with
CDR DICOM 3.5 and
Recommended WAN
Configuration
c r e a t i n g t h e i m a g e Figure 6Under Licensing Mode, please select the appropriate licensing mode and number of licenses.
Figure 7
MS SQL 2000 Server with
CDR DICOM 3.5 and
Recommended WAN
Configuration
c r e a t i n g t h e i m a g eSTEP 2:
• Only to be completed by ex i s t i n g u s e r s o f C D R D I C O M 3 . 0 . 1 w i t h a n e x i s t i n g M S S Q L 2 0 0 0 S e r v e r D I C O M d a t a b a s e . A l l o t h e r u s e r s p r o c e e d t o S t e p 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.
MS SQL 2000 Server with
CDR DICOM 3.5 and
Recommended WAN
Configuration
c r e a t i n g t h e i m a g e
MS SQL 2000 Server with
CDR DICOM 3.5 and
Recommended WAN
Configuration
c r e a t i n g t h e i m a g e
MS SQL 2000 Server with
CDR DICOM 3.5 and
Recommended WAN
Configuration
c r e a t i n g t h e i m a g eOn 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.
MS SQL 2000 Server with
CDR DICOM 3.5 and
Recommended WAN
Configuration
c r e a t i n g t h e i m a g eThis 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..
MS SQL 2000 Server with
CDR DICOM 3.5 and
Recommended WAN
Configuration
c r e a t i n g t h e i m a g eAfter 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.
MS SQL 2000 Server with
CDR DICOM 3.5 and
Recommended WAN
Configuration
c r e a t i n g t h e i m a g e
MS SQL 2000 Server with
CDR DICOM 3.5 and
Recommended WAN
Configuration
c r e a t i n g t h e i m a g eOn 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
MS SQL 2000 Server with
CDR DICOM 3.5 and
Recommended WAN
Configuration
c r e a t i n g t h e i m a g e
MS SQL 2000 Server with
CDR DICOM 3.5 and
Recommended WAN
Configuration
c r e a t i n g t h e i m a g eSTEP 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.
MS SQL 2000 Server with
CDR DICOM 3.5 and
Recommended WAN
Configuration
c r e a t i n g t h e i m a g e
MS SQL 2000 Server with
CDR DICOM 3.5 and
Recommended WAN
Configuration
c r e a t i n g t h e i m a g e
MS SQL 2000 Server with
CDR DICOM 3.5 and
Recommended WAN
Configuration
c r e a t i n g t h e i m a g e
MS SQL 2000 Server with
CDR DICOM 3.5 and
Recommended WAN
Configuration
c r e a t i n g t h e i m a g eAfter 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.
MS SQL 2000 Server with
CDR DICOM 3.5 and
Recommended WAN
Configuration
c r e a t i n g t h e i m a g eSTEP 4:
•
To be completed by all usersModifying 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
MS SQL 2000 Server with
CDR DICOM 3.5 and
Recommended WAN
Configuration
c r e a t i n g t h e i m a g e
MS SQL 2000 Server with
CDR DICOM 3.5 and
Recommended WAN
Configuration
c r e a t i n g t h e i m a g eVerify 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.
