SQL Server 2005Michael 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 that. If you often repurpose information in different contexts you want to decompose the data and "normalize" it to the extend that it simplifies that. 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 Michael > -----Original Message----- > From: http://xquery.com/mailman/listinfo/talk > [mailto:http://xquery.com/mailman/listinfo/talk] On Behalf Of Ronald Bourret > Sent: Thursday, January 26, 2006 10:54 PM > To: http://xquery.com/mailman/listinfo/talk > Subject: Re: 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 > > _______________________________________________ > http://xquery.com/mailman/listinfo/talk > http://xquery.com/mailman/listinfo/talk >
PURCHASE STYLUS STUDIO ONLINE TODAY!
Purchasing Stylus Studio from our online shop is Easy, Secure and Value Priced!
Download The World's Best XML IDE!
Accelerate XML development with our award-winning XML IDE - Download a free trial today!
Subscribe in XML format