E
Eric G
I have a few questions concerning importing external data.
Right now with our db I import external data a few times a year, which
requires several steps. During import I need to ensure that the
columns have been separated correctly. Then I need to insert a field
title for each column. Then I need to name the table. Then I need to
rename the old table, making way for the new table. Then I need to
establish the relationships between the new table and other tables.
Now for my questions. Is it possible to automate much or all of the
above?
Although it would be nice to have this automation at my disposal, I'm
asking for some potential new users.
My db may be distributed/sold to other schools for their use.
Once the db is setup on their system it is relatively easy to
maintain.
The main setup issues would be placing the backend on the server and
the frontend on the various frontend machines.
Then the above importation of data would need to be completed for a
few tables.
When db developers sell their software to businesses/institutions do
they try to make the software as maintenance-free as possible, or do
they leave certain setup/maintenance functions outside the
user/admin's domain? I'm thinking of the above setup plus compacting
and backing up the db etc.
Thanks for your guidance. Eric
Right now with our db I import external data a few times a year, which
requires several steps. During import I need to ensure that the
columns have been separated correctly. Then I need to insert a field
title for each column. Then I need to name the table. Then I need to
rename the old table, making way for the new table. Then I need to
establish the relationships between the new table and other tables.
Now for my questions. Is it possible to automate much or all of the
above?
Although it would be nice to have this automation at my disposal, I'm
asking for some potential new users.
My db may be distributed/sold to other schools for their use.
Once the db is setup on their system it is relatively easy to
maintain.
The main setup issues would be placing the backend on the server and
the frontend on the various frontend machines.
Then the above importation of data would need to be completed for a
few tables.
When db developers sell their software to businesses/institutions do
they try to make the software as maintenance-free as possible, or do
they leave certain setup/maintenance functions outside the
user/admin's domain? I'm thinking of the above setup plus compacting
and backing up the db etc.
Thanks for your guidance. Eric