ESdat Forums
»
Forums
»
ESdat
»
Transfer from Access to SQL
Rank: Member
Groups: Registered
Posts: 12 Location: Calgary, Canada
|
We have a few offices that have remained on the Access platform and are now eager to transfer to SQL. I'd like to help them along the way so have been looking up information pertaining to both EDIF files and GEDT files. I'm uncertain which should be used. Essentially over the past number of years many Access databases have been developed and now all of that information should be transferred to the SQL database - I don't want to change all the look up information on the existing main database but I'm not sure that existing original data (in Access) will have the same look up info. Should there be a new database created for these ? I'd prefer not to open another as I'm finding it's already confusing to find data as we have 3 existing seperate databases on SQL and it's hard to regulate who's uploading to which database.... (we have offices all over western Canada). In some ways I feel like the one that's come late to the party when things are starting to get a bit messy. Some advice and direction would be greatly appreciated. I'd like to try it out and then I'll likely write up a procedure so that we don't have this issue continue.
|
|
|
|
Rank: Administration
Groups: Registered, Administrators Posts: 259 Location: Ballina
Was thanked: 8 time(s) in 8 post(s)
|
Hello, The EDIF file is the preferred way to export data from the Access version of ESdat and import it into the SQL Server Version. See http://www.ESdat.net/ESdathelp/index.html?edif.htm It may be necessary to add some ChemCodes to the SQL Server database zRef_Chemistry_Lookup table, if the Access database references compounds (ChemCodes) that are not in the SQL Server database. You can add them in the normal manner as a invalid ChemCode is flagged during import, or upload in bulk if you include the zRef_Chemistry_Lookup in your import. As for having multiple SQL Server databases, the need for this is very rare, and all users should be using the one SQL Server database, although there can be certain situations where this may not be desirable. Alex
|
|
|
|
Rank: Member
Groups: Registered
Posts: 12 Location: Calgary, Canada
|
Thanks for the advice Alex! I will have some time soon to start transferring over to SQL - once that is done I'll start looking at why we have so many SQL databases.... I believe there was some justification for it in the past- having to do with different preferences for chem orders I think. We do have offices that are in different provinces so the way we need to export data to tables for reporting differs regionally. Blerg! I think I remember seeing some mention of an update in the 4.3 version that allows for saving of different profiles? Would this allow for us to have different chem order preferences but still maintain all data on a single database? If so this may be a project for me to tackle in the slow winter season. Cheers, Rhia
|
|
|
|
Rank: Administration
Groups: Registered, Administrators Posts: 498 Location: Byron Bay Was thanked: 19 time(s) in 19 post(s)
|
Hello Rhia, Yes, in 4.3 and higher different "Chem Profiles" can be set up with different output units / orders etc.. for the same compound. In previous versions each compound could only have a single specified output unit for each Matrix (water, soil etc..). Warwick
|
|
|
|
ESdat Forums
»
Forums
»
ESdat
»
Transfer from Access to SQL
You cannot post new topics in this forum.
You cannot reply to topics in this forum.
You cannot delete your posts in this forum.
You cannot edit your posts in this forum.
You cannot create polls in this forum.
You cannot vote in polls in this forum.