""Yuan Shao"" <v-yshao (AT) online (DOT) microsoft.com> wrote
Quote:
Hi Trapulo,
Thanks for your feedback. According to your description, I understand that
you want to import data having different data types to the Table in the
SQL
Server with the same data format. If I have misunderstood you, please feel
free to let me know. |
You are right.
I need to create a catalog of object, with some attributes standard and some
attributes personalized for each type of object loaded into the catalog.
Without limit about number and type of this objects (if I haven't this
requirement, I can use some table with one-to-one relationship).
Quote:
Based on my experience, it seems that there is not an easy way to meet
your
requirements in regards to the SQL Server. The Data in Database needs
regular storage format. It is possible that you can force storing the data
having different data types to the table via heavy work, but you need to
pay more attention to maintain this table. Also, when you want to retrieve
the data from the table, is the data in the table still significative as
the one before? It is appreciated that you can tell me your root concerns. |
I need to catalog data with a flexible description schema. My primary
information are registered inside "normal" relational fields. The flexible
fields are the problem. I need some search features about this fields, but
they are not the primary search keys. If I want only store and retrieve
extended information, I'll use a text field to store xml data and then the
application can understand it. But I need to make some search on data
contained in this fields...
The best solution I've found until today is XML datatype field in SQL Server
2003 Yukon, that support xpath filters on xml fields and can "decode" the
string inside the field to perform search as a normal "where" statement. But
I can't have SQL 2003, so I need an alternative solution...
Thanks