1. Connection changes in Scribe Starting with version 7.9.0
Prior to Insight version all connection configuration information was saved in the DTS
Starting with all connections are stored globally so that they can be used in multiple DTS’s
Common connection information is in the ScribeInternal DB
DTS specific settings remain stored in the DTS
7.9.1 Has new features to allow you to select an existing connection
Prior to that you were forced to create a new connection even if you knew an existing connection would work

2. Connection Manager
A new connection is required for each unique combination of Connection Settings (except password)
This also includes any adapter properties that are considered part of the connection
IsConnectionProperty = Yes
Edit DTS – Search XML for Adapter Properties

3. ScribeInternal Connection Data
Connection information is stored in the DataProvider or DRSProperties tables in ScribeInternal
Only adapter properties where IsConnectionProperty = Y are stored in DRSProperties

4. Adding a New Connection
Existing connections are now shown in the Connection Manager
Select an existing connection or create a new one
Naming convention has become an important consideration

5. Converting Existing DTS’s
If no Global connection exist – connect as you usually would
Note: The creation of a connection in the Connection Manager is not the same as connecting to a source or target in the DTS. These are two distinct and separate operations.

6. Cascading Connection Changes
Connections can be cascaded to other DTS’s in the same folder and in any subfolders
Only DTS’s that fully match the DataProvider connection and DSRProperties entries are selected

7. Converting Existing DTS’s
In prior versions of Scribe, it was possible for different connections to use the same name.
For example in CRM the connection name could be Adapter for Dynamics CRM.
But the connection URL or type (OnPremise, Online or IFD) would be different
Global connections require a separate connection and name/label for each
When a DTS is opened and the connection information doesn't match any entries in the Connection Manager, Scribe will prompt you to create a new connection or select an existing connection

8. Converting Existing DTS’s
Once a connection has been added to or selected from the Connection Manager, you still need to connect in the DTS

9. Connection Manager & DTS Connections
The connection Manager now shows all of the connections
Those utilized by the DTS will have S, T, O usage designation
Only those connections utilized by the DTS are validated and show in Red if there are connection issues

10. Connection Settings
DTS Connection Settings are not enabled until the connection has been added to the DTS
This is not the same as adding to the Connection Manager

11. DTS Conversion Considerations
Make a backup of existing DTS’s – Copy the Collaborations folder to another location
Review the existing connections — Familiarize yourself with the connection properties that each DTS uses.
Plan the new connections — Determine the sets of connection properties that you need to configure to meet the requirements of all DTS files. Although you convert DTS files individually, you can cascade the changes to other DTS files that use similar connections.
Set a connection naming convention — Define a naming convention for global connections that indicate the connection type and properties.
Enable DTS Backup Option - Be sure to choose the Create Backup option if prompted
This option may have already been set in an earlier version of Scribe
Delete any earlier versions of the .bak files so it will be easier to see what files have been converted
Cascade Changes – Using the cascade feature when converting connections will prevent having to create new connections when an existing connection already exists.

12. Deleting a Global Connection
Deactivates the connection in the database.
If you open a DTS that uses a deleted connection, the Connection Manager displays the missing connection in red
If you define a new connection that matches the name and properties of a deleted connection the original connection is reactivated

13. Removing a DTS Connection
Removes a Target connection only from the current DTS

14. Migrating DTS to Different Environment
In the past, DTS connections were stored with the DTS. This allowed you to simply copy the DTS to a new server and change the connection information
Since the connections are now stored in the database, the best way to move DTS’s between environments is to use the Console Export/Import utility

15. DTS Connection Enhancements in 7.9.1
There is now the ability to change/swap out target connections in 7.9 DTS files with any connection in the database using the Change button.
This feature is similar to replace on the source, so the user will not need to modify the links or rebuild target steps.

16. DTS Connection Enhancements in 7.9.1
Exact matches are listed when the Show only connections with matching parameters is checked
Unchecking the option will expose all connections
Choosing an incompatible connection will remove links from the DTS

17. Cascading Connection Changes to Other DTS’s
When migrating DTS’s from version and earlier to and later you may have a scenario where DTS’s that use the same connection are located in different folders. By default, Scribe will ask you if you want to cascade the changes down to other DTS’s in the same folder and any sub-folders. However it will not cascade the changes to other sibling folders as shown by the group of folders on the left. One way to work around this is to create a parent folder and copy all of the DTS’s into the parent folder. Then edit and modify each DTS and allow the changes to cascade down to all of the other DTS’s. When finished, delete the parent folder.

18. DTS Connection Enhancements in 7.9.1
Known Issues
After creating a new target connection, you must save and close the DTS to enable the Change button in Configure Steps/Data Objects Tab.
Workbench crashes when S and T are the same and the user is attempting to change target after changing the source, and not saving the DTS before changing the target.
Change button is not enabled when the source & target are the same – Workaround:
Create a connection in the Connection Manager identical to the original connection
Change the Source connection to the new/cloned connection
Save the DTS or the Workbench will crash
Change the target connection (Change button now enabled)
Change the source connection back to the original connection

19. Misc. Info
Any connection that is not assigned a usage role, such as Source or Target in the older DTS, is converted to a Target connection in Insight version 7.9.0
In Insight version and later, the Import/Export wizard includes the connection information in the export package.