|
|
Posted by David Portas on 10/18/02 11:37
adi wrote:
> Hi all,
> My program is a central data processing application built in ASP.
> We have different companies that use different web pages on another web
> application (from different countries) to load some inventory data
> (merchandise - clothes).
>
> Here is my requirement: Load different types of data (in different
> formats) into a common set of tables, to do this I have to first
> filter, do lookup's, use cross-reference tables on this data and then
> load it into a couple of tables.
> Since data is so different everytime, I want to have one main stored
> procedure in which I can build the table (I know the format of this
> data so I know what columns/types to create) into which I will feed the
> data.
> After this I will create other stored procs/udf's that reference this
> table (probably from the same main stored proc) 'cleanse' the data
> before loading into the actual tables.
>
> How feasible is my approach? (if you can call it one :-) I do not want
> to have seperate tables for each country, that will be too many and so
> this plan...
>
> If not any other ideas will be really helpful.
>
> thanks much
This is a very common requirement and there is a whole industry of
solutions for it. Microsoft's offering is Integration Services (or DTS
prior to SQL Server 2005). Since that comes free with the database
(Standard and Enterprise) it's the obvious place to start.
http://www.microsoft.com/sql/technologies/integration/default.mspx
--
David Portas, SQL Server MVP
Whenever possible please post enough code to reproduce your problem.
Including CREATE TABLE and INSERT statements usually helps.
State what version of SQL Server you are using and specify the content
of any error messages.
SQL Server Books Online:
http://msdn2.microsoft.com/library/ms130214(en-US,SQL.90).aspx
--
Navigation:
[Reply to this message]
|