Database Pointers & Updates

Questions, answers, and tips about the installation and configuration of DraftLogic Electrical

Database Pointers & Updates

Postby forumadmin » Mon Aug 27, 2012 4:56 pm

Until release 3.0.0.603, there has been two very divergent methods of performing a DraftLogic Electrical database update:

Since early 2012, users with both DraftLogic Electrical Server and Client on their workstation could just overwrite the databases (notwithstanding a database merge if any rooms, luminaires, etc were desired to be retained). This was because we used the '(local)' path in the DATA_SOURCE table by default. This didn't work out so well for sites where DraftLogic Electrical Server has been installed separate from DraftLogic Electrical Client, because...well, the database was not local to the client anymore! Thus we had to have a definitive path in the DATA_SOURCE table to the SQL Server over the local area network.

Anyone who has implemented a DraftLogic Electrical database update at a site where DraftLogic Electrical Server has been installed separate from DraftLogic Electrical Client has seen the 'old' way of retaining the database pointers. Prior to release 3.0.0.603 [shipped end of August 2012], it used to be that you had to update pointers in the DATA_SOURCE table if your site had the Microsoft SQL databases on a different computer. Since this left the database pathing in a database that was being overwritten, there was a necessary back-up of that path before the update followed by pasting the correct path back into the newly updated database, a few minutes of inconvenience.

In release 3.0.0.603 and later, you can still use the old method of manually maintaining the paths in DATA_SOURCE if you desire and now you have a new option: one-time configuration of UDL files for all three databases (and a fourth for IntelliBid if you are linking your DraftLogic Electrical to your ConEst IntelliBid).

Basically there may now be a UDL file for each of the DBs (Config, Control and DraftLogic). If a UDL file is present in the server/config dir then it will be used. Otherwise the DATA_SOURCES table will be used (i.e. as things have always worked). The only exception is that the Config DB connection string MUST be in a UDL, as has always been the case.

i.e.:
1) Config DB: The connection to the config DB will continue to be made as usual (i.e. via the connection string in the server/config/ConfigDB.UDL).
2) Control DB: The connection string will be read from server/config/ControlDB.UDL. If no such UDL file is found* then the connection string will be read from the DATA_SOURCES table.
3) DraftLogic DB: The connection string will be read from server/config/DraftLogicDB.UDL. If no such UDL file is found* then the connection string will be read from the DATA_SOURCES table.

* In some instances if the UDL file is present but is “bad” in some way then the DATA_SOURCE connection string will be used instead.

To create the new UDL files:
1) Create a copy of the existing ConfigDB.UDL.
2) Rename to ControlDB.UDL.
3) Double-click the ControlDB.UDL and change the “Select the database on the server” to “DL-Control”.
4) Create a copy of the existing ConfigDB.UDL.
5) Rename to DraftLogicDB.UDL.
6) Double-click the DraftLogic.UDL and change the “Select the database on the server” to “Draftlogic”.

After doing this, you no longer have to manually manage database paths in DATA_SOURCE for each database update! Make a backup of your UDL files to a directory outside the DraftLogic Electrical file tree in case you want to do a complete uninstall/reinstall at some point.

Note that in the rare cases where a site has client/server installed on each workstation but is running a shared SQL Server, you will need to copy the UDL files that you create to the Server\Config directories on each workstation.
forumadmin
Site Admin
 
Posts: 87
Joined: Fri Sep 11, 2009 5:46 am

Return to Installation

Who is online

Users browsing this forum: No registered users and 1 guest

cron