Please start any new threads on our new site at https://forums.sqlteam.com. We've got lots of great SQL Server experts to answer whatever question you can come up with.

 All Forums
 SQL Server 2000 Forums
 SQL Server Development (2000)
 XML to database Design question

Author  Topic 

BartMan
Starting Member

22 Posts

Posted - 2004-04-12 : 11:25:48
Greetings,

I was wondering what the best way to collate data from xml files, and from a table found in my sql server into a central format without permantely updating the table (found in the sql server).

Basically I want to add the information found in the xml files to the table, and not have a permant update. But so a user can run a query on it, and then the information is removed for another user to perform a query. (Users can come up with the strangest requests :)).

I have thought about using a temporary table and filling it with data from the xml files as well as the data from the original table, but I was wondering if there were any other opinions as to how I do this.

Thanks in advance for any suggestions.

derrickleggett
Pointy Haired Yak DBA

4184 Posts

Posted - 2004-04-12 : 11:33:33
Is it going to be specific to one user, or do you want all users to see the "merged" result?

MeanOldDBA
derrickleggett@hotmail.com

When life gives you a lemon, fire the DBA.
Go to Top of Page

BartMan
Starting Member

22 Posts

Posted - 2004-04-12 : 14:41:38
quote:
Originally posted by derrickleggett

Is it going to be specific to one user, or do you want all users to see the "merged" result?

MeanOldDBA
derrickleggett@hotmail.com

When life gives you a lemon, fire the DBA.



At this time 1 user to see the result, although there was talk of expanding this to all users in the future.
Go to Top of Page

derrickleggett
Pointy Haired Yak DBA

4184 Posts

Posted - 2004-04-12 : 18:28:26
A few ways you could handle this.

Add a user_id to the table to make some data available only to certain users.
--This would be more of a permanent solution though and would involve changing all your code to filter or not filter.

Create a seperate table that's permanent.
--You would put both sets there.
--You would have to run a sync process each time it's needed.
--Can be costly.
--Can be used to switch users over in stages though.

Create a temp table.
--Would only be good per session.

I'm sure you've probably already thought of all these though. There's no magical way around this.

MeanOldDBA
derrickleggett@hotmail.com

When life gives you a lemon, fire the DBA.
Go to Top of Page

BartMan
Starting Member

22 Posts

Posted - 2004-04-13 : 10:55:50
quote:
Originally posted by derrickleggett

A few ways you could handle this.

Add a user_id to the table to make some data available only to certain users.
--This would be more of a permanent solution though and would involve changing all your code to filter or not filter.

Create a seperate table that's permanent.
--You would put both sets there.
--You would have to run a sync process each time it's needed.
--Can be costly.
--Can be used to switch users over in stages though.

Create a temp table.
--Would only be good per session.

I'm sure you've probably already thought of all these though. There's no magical way around this.

MeanOldDBA
derrickleggett@hotmail.com

When life gives you a lemon, fire the DBA.



Thanks for your input and the idea about the user, I didn't think of that one.
Go to Top of Page
   

- Advertisement -