Login ProductsSalesSupportDownloadsAbout |
Home » Technical Support » ElevateDB Technical Support » Support Forums » ElevateDB General » View Thread |
Messages 1 to 3 of 3 total |
Changing my data location |
Wed, Jan 19 2011 5:10 PM | Permanent Link |
Jeff Newlin Lightspeed | He everyone -
I have created a database with a certain path (for example c:\StartLocation\db) and now I want to take all that data and store it to another location and remove the original. I copied all of the data files over to the new location (example c:\newlocation\db) including the EDBDatabase.EDBLck and the EDBConfig.EDBLck files, started up the server with it's new "config folder" - then deleted everything from the old location. But it doesn't connect. I assume that somehow I need to change the EDBDatabase.EDBLck or the EDBConfig.EDBLck files to reflect the new path. But I can't seem to locate how to do that. Thanks for all the help! I'm sure I'm missing something small here. Jeff |
Wed, Jan 19 2011 7:33 PM | Permanent Link |
Tim Young [Elevate Software] Elevate Software, Inc. timyoung@elevatesoft.com | Jeff,
<< I have created a database with a certain path (for example c:\StartLocation\db) and now I want to take all that data and store it to another location and remove the original. I copied all of the data files over to the new location (example c:\newlocation\db) including the EDBDatabase.EDBLck and the EDBConfig.EDBLck files, started up the server with it's new "config folder" - then deleted everything from the old location. But it doesn't connect. I assume that somehow I need to change the EDBDatabase.EDBLck or the EDBConfig.EDBLck files to reflect the new path. But I can't seem to locate how to do that. >> See here for information on how to do it: http://www.elevatesoft.com/supportfaq?action=view&category=edb&question=change_database_path Also, as a general rule, you should try to keep the edbconfig.* files in a different location from the database files. I recommend that you use a structure like this: \MyApp (Configuration path) \MyApp\Data (Database path) The beauty of this type of naming convention is that you can define the database with a relative path name, like this: CREATE DATABASE MyDatabase PATH 'Data' This will tell EDB that you want MyDatabase's path to always be relative to the configuration path, so if you move the whole directory structure to a different location or drive, you only need to change the configuration path. Another option is the virtual configurations that were added in 2.04, which allow you to skip having an on-disk configuration file at all. Check the 2.04 release notes for more information, as well as here: http://www.elevatesoft.com/manual?action=viewtopic&id=edb2&product=d&version=7&topic=Configuring_Starting_Engine under "Configuration Path". Finally, you mentioned copying the .edblck files - don't both with them. You can even delete them without consequence. They're simply used for file-sharing locking and are always empty. -- Tim Young Elevate Software www.elevatesoft.com |
Wed, Jan 19 2011 11:32 PM | Permanent Link |
Jeff Newlin Lightspeed | Thank you Tim that's got me going!
Jeff "Tim Young [Elevate Software]" wrote: Jeff, << I have created a database with a certain path (for example c:\StartLocation\db) and now I want to take all that data and store it to another location and remove the original. I copied all of the data files over to the new location (example c:\newlocation\db) including the EDBDatabase.EDBLck and the EDBConfig.EDBLck files, started up the server with it's new "config folder" - then deleted everything from the old location. But it doesn't connect. I assume that somehow I need to change the EDBDatabase.EDBLck or the EDBConfig.EDBLck files to reflect the new path. But I can't seem to locate how to do that. >> See here for information on how to do it: http://www.elevatesoft.com/supportfaq?action=view&category=edb&question=change_database_path Also, as a general rule, you should try to keep the edbconfig.* files in a different location from the database files. I recommend that you use a structure like this: \MyApp (Configuration path) \MyApp\Data (Database path) The beauty of this type of naming convention is that you can define the database with a relative path name, like this: CREATE DATABASE MyDatabase PATH 'Data' This will tell EDB that you want MyDatabase's path to always be relative to the configuration path, so if you move the whole directory structure to a different location or drive, you only need to change the configuration path. Another option is the virtual configurations that were added in 2.04, which allow you to skip having an on-disk configuration file at all. Check the 2.04 release notes for more information, as well as here: http://www.elevatesoft.com/manual?action=viewtopic&id=edb2&product=d&version=7&topic=Configuring_Starting_Engine under "Configuration Path". Finally, you mentioned copying the .edblck files - don't both with them. You can even delete them without consequence. They're simply used for file-sharing locking and are always empty. -- Tim Young Elevate Software www.elevatesoft.com |
This web page was last updated on Thursday, May 23, 2024 at 07:54 PM | Privacy PolicySite Map © 2024 Elevate Software, Inc. All Rights Reserved Questions or comments ? E-mail us at info@elevatesoft.com |