|
Home > Archive > Commerce Server General > March 2004 > Modifying Commerce Server 2002 Tables
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
Modifying Commerce Server 2002 Tables
|
|
| Samer 2004-03-23, 10:42 am |
| Hi,
Say you need to add more information to one of the CS
tables OrderGroup, UserObject, ... I know that you can add
your own columns to the tables and gain read/wite access
through the API...
But the CS documentation literally says "Do not modify
these tables for any reason."
So how could I extend the tables schema? What's the best
practice?
Thanks in advance,
Samer
| |
| Willie Chiu 2004-03-23, 12:42 pm |
| Samer,
You could add the new data into the marshall field. It's good when you have
good design to keep track of it (a few new fields). But when you have more
than 5 fields or so, you should extend your schema. The reason that you
shouldn't modify the schema is that when it comes to upgrading to the next
version of CS, things will get hairy and the upgrade tool probably will not
support your extended schema. You'll probably have to end up performing a
manual conversion.
We've done it because our client wanted so many different new fields other
than the ones coming out of the box.
Willie
"Samer" <anonymous@discussions.microsoft.com> wrote in message
news:1237801c410e5$e13e05b0$a101280a@phx
.gbl...
> Hi,
>
> Say you need to add more information to one of the CS
> tables OrderGroup, UserObject, ... I know that you can add
> your own columns to the tables and gain read/wite access
> through the API...
>
> But the CS documentation literally says "Do not modify
> these tables for any reason."
>
> So how could I extend the tables schema? What's the best
> practice?
>
> Thanks in advance,
> Samer
>
| |
| Clayton C. Peddy 2004-03-23, 8:37 pm |
| Samer,
The profile storage tables, such as UserObject, Addresses, etc are intended
to be extended. One bit of caution though, be careful when removing /
changing existing columns from the default objects as this may adversely
affect other CS systems.
Other customizations can work for the other CS systems (table schema
changes), however please bear in mind that these changes will need to be
carefully documented, as Service Packs and product upgrades may be
negatively affected and require either re-application or re-design to make
them work properly.
Most schema changes / extensions can be done without changing the underlying
tables directly. If you have any schema changes in mind, I may be able to
provide some assistance.
Clayton
"Samer" <anonymous@discussions.microsoft.com> wrote in message
news:1237801c410e5$e13e05b0$a101280a@phx
.gbl...
> Hi,
>
> Say you need to add more information to one of the CS
> tables OrderGroup, UserObject, ... I know that you can add
> your own columns to the tables and gain read/wite access
> through the API...
>
> But the CS documentation literally says "Do not modify
> these tables for any reason."
>
> So how could I extend the tables schema? What's the best
> practice?
>
> Thanks in advance,
> Samer
>
| |
|
| Thanks for the response Willie
- First, I don't think I can make use of the marshaled
fields. I need to query this extra information and do some
reporting based on it.
- Though, from my experience I can tell that the CS
database schema hasn't changed much between cs2000 and
cs2002. But I'm still cautious in this regard. I hoped to
find any MS documents talking about this issue 
- When you say "We've done it because our client wanted
so....". Do you mean that you have modified the default CS
database schema (added columns? deleted columns?) you
faced any issues? any tips?
Regards,
Samer
>-----Original Message-----
>Samer,
>You could add the new data into the marshall field. It's
good when you have
>good design to keep track of it (a few new fields). But
when you have more
>than 5 fields or so, you should extend your schema. The
reason that you
>shouldn't modify the schema is that when it comes to
upgrading to the next
>version of CS, things will get hairy and the upgrade tool
probably will not
>support your extended schema. You'll probably have to
end up performing a
>manual conversion.
>
>We've done it because our client wanted so many different
new fields other
>than the ones coming out of the box.
>
>Willie
>
>
>"Samer" <anonymous@discussions.microsoft.com> wrote in
message
> news:1237801c410e5$e13e05b0$a101280a@phx
.gbl...
add[color=darkred]
>
>
>.
>
| |
|
| Thanks Clayton,
My comments inline
>-----Original Message-----
>Samer,
>
>The profile storage tables, such as UserObject,
Addresses, etc are intended
>to be extended. One bit of caution though, be careful
when removing /
>changing existing columns from the default objects as
this may adversely
>affect other CS systems.
[Samer]: Is there any document stating that it's allowed
to modify those tables. The cs documentation is against
that!
>
>Other customizations can work for the other CS systems
(table schema
>changes), however please bear in mind that these changes
will need to be
>carefully documented, as Service Packs and product
upgrades may be
>negatively affected and require either re-application or
re-design to make
>them work properly.
>
>Most schema changes / extensions can be done without
changing the underlying
>tables directly. If you have any schema changes in mind,
I may be able to
>provide some assistance.
>
[Samer]: Mainly, I need to add extra information on:
1) The order level (OrderGroup table)
2) The basket level (BasketGroup table)
3) Extend UserObject profile (UserObject table) and
possibly integrate with Active Directory.
4) ...
>Clayton
>
>"Samer" <anonymous@discussions.microsoft.com> wrote in
message
> news:1237801c410e5$e13e05b0$a101280a@phx
.gbl...
add[color=darkred]
>
>
>.
>
|
|
|
|
|