[xquery-talk] SQL Server 2005

Michael Rys mrys at microsoft.com
Fri Jan 27 13:07:07 PST 2006

That is a multi-dimensional benefit/cost optimization.

If you have lots of relational business processes, you want to tie into
If you often repurpose information in different contexts you want to
decompose the data and "normalize" it to the extend that it simplifies

If you mainly need to find documents, you keep the information together.

If your datastructure is semi-structure or markup structured, you want
to keep it in XML.

Then there are query and update performance/loads, concurrency control
issues etc to be taken into account.

Just normal data modeling decisions ;)

Best regards

> -----Original Message-----
> From: talk-bounces at xquery.com 
> [mailto:talk-bounces at xquery.com] On Behalf Of Ronald Bourret
> Sent: Thursday, January 26, 2006 10:54 PM
> To: talk at xquery.com
> Subject: Re: [xquery-talk] SQL Server 2005
> Michael Rys wrote:
> > I think that the addition of XML datatypes, XML Schema collections,
> > XQuery to the relational databases are aimed exactly at 
> these type of
> > problems.
> > 
> > You can deploy and manage all your data with a single DB instead of
> > having to federate and manage two completely independent silos....
> Agreed. But how do you decide what to store as XML and what to store 
> relationally?
> -- Ron
> _______________________________________________
> talk at xquery.com
> http://xquery.com/mailman/listinfo/talk

More information about the talk mailing list