By using this site, you agree to our updated Privacy Policy and our Terms of Use. Manage your Cookies Settings.
424,665 Members | 1,430 Online
Bytes IT Community
+ Ask a Question
Need help? Post your question and get tips & solutions from a community of 424,665 IT Pros & Developers. It's quick & easy.

importing data from customer workstation

P: n/a
Is there some some standard for this type of database issue?

We have an internet application. db2 aix v8.1. was5.0.
Our customers want to be able to "upload" or "import" data into our
database.
for example, the customer would have the info in a standardized format
such as a spreadsheet or text file.
the customer would submit the file at their convenience within the
appication. Somehow the data would eventually imported into the
database if it passes the integrity checks etc. after a certain amount
of time (batch, or on demand)
they could then log in to the application and see the data in the
proper format.
Sounds like an excellent idea. sounds viable.

the problem I forsee is this. even though the import of data is
successful, there will no doubt be problems such - missing info,
incorrect info, etc
The customer will want to redo the import at their convenience. since
the data will have been imported into many tables, a mass delete may
harm performance, cause table locks, fill logs etc. our app is full of
many small, fast , efficient transactions.
I dont like the idea of a customer bringing down the app for the rest
of the world by a runaway delete.
with the RI, some of the deletes might take minutes to and hour to
complete.

any recommendations/ideas/experiences?
some ideas I had were:
1) schedule a delete of the data off hours.
2) have a staging area where the customer could preview the data
before committing

thanks in advance
ap
Nov 12 '05 #1
Share this Question
Share on Google+
1 Reply


P: n/a
I would go for a staging area per customer.
That would also solve problems of two persons trying to import into the
same table at the same time, which might cause lock timeouts. Deleting
data from the staging area can be done real fast by importing from an
empty file.

Alexander Pope wrote:
Is there some some standard for this type of database issue?

We have an internet application. db2 aix v8.1. was5.0.
Our customers want to be able to "upload" or "import" data into our
database.
for example, the customer would have the info in a standardized format
such as a spreadsheet or text file.
the customer would submit the file at their convenience within the
appication. Somehow the data would eventually imported into the
database if it passes the integrity checks etc. after a certain amount
of time (batch, or on demand)
they could then log in to the application and see the data in the
proper format.
Sounds like an excellent idea. sounds viable.

the problem I forsee is this. even though the import of data is
successful, there will no doubt be problems such - missing info,
incorrect info, etc
The customer will want to redo the import at their convenience. since
the data will have been imported into many tables, a mass delete may
harm performance, cause table locks, fill logs etc. our app is full of
many small, fast , efficient transactions.
I dont like the idea of a customer bringing down the app for the rest
of the world by a runaway delete.
with the RI, some of the deletes might take minutes to and hour to
complete.

any recommendations/ideas/experiences?
some ideas I had were:
1) schedule a delete of the data off hours.
2) have a staging area where the customer could preview the data
before committing

thanks in advance
ap


--
Anton Versteeg
IBM Certified DB2 Specialist
IBM Netherlands
Nov 12 '05 #2

This discussion thread is closed

Replies have been disabled for this discussion.