This is a multi-part message in MIME format...

--vNxYV1QFOmx3QsLWETUTxtb7Q
Content-Type: text/plain
Content-Transfer-Encoding: 8bit

hi,
 I have simple application provider type of application where my server's 
database is MS access type. I just cant find any use of using a complicated XML 
database.
can any one tell me unless i have a distributed application ..why should i 
update to an XML d.base ,if at all?Is it a must in .NET to use XML d_base?

thankx in advance
sriram




------------------------------------------------------------
WWW.COM - Where the Web Begins! http://www.www.com

This is a multi-part message in MIME format.

------=_NextPart_000_0061_01C2115A.9A782890
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit


It is rare that you would use it as a means of persisting data.  I have only
used it for that purpose when I had a small amount of data that I wanted to
be readable and editable from a text editor.

Normally XML would be used as a means of interchanging data between loosely
coupled systems e.g in a hetrogenous environment you may wish to communicate
data from your MS system to another non-MS system suvh as unix.

It can inefficient to use XML as your means of storing data especially when
you have large amounts of it.

For those wishing to have the benefits of SQL database along with the
flexibility of XML you can use Datasets to easily work between the two
sources.


 -----Original Message-----
From: sriram c [mailto:cpavan@w...]
Sent: Tuesday, 11 June 2002 1:54 PM
To: ASP+
Subject: [aspx] why XML?


hi,
 I have simple application provider type of application where my server's
database is MS access type. I just cant find any use of using a complicated
XML
database.
can any one tell me unless i have a distributed application ..why should i
update to an XML d.base ,if at all?Is it a must in .NET to use XML d_base?

thankx in advance
sriram




------------------------------------------------------------
WWW.COM - Where the Web Begins! http://www.www.com

This is a multi-part message in MIME format.

------=_NextPart_000_0078_01C21128.68648F60
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

IMHO there is no need to to go for an XML database. They are not 
obligatory in .NET

   The relational DB model serves very well in most instances.

    One of the problems with XML is that it is  hierarchical and 
therefore has some of the problems
 which were associated with Hierarchical dbs and which the relational 
model replaced. For those of
you old enough to remember - I made my first DB application in 1974.


Cheers, Phil
  ----- Original Message -----
  From: sriram c
  To: ASP+
  Sent: Tuesday, June 11, 2002 4:54 AM
  Subject: [aspx] why XML?


hi,
 I have simple application provider type of application where my 
server's
database is MS access type. I just cant find any use of using a 
complicated XML
database.
can any one tell me unless i have a distributed application ..why should 
i
update to an XML d.base ,if at all?Is it a must in .NET to use XML 
d_base?

thankx in advance
sriram




------------------------------------------------------------
WWW.COM - Where the Web Begins! http://www.www.com

  


_____________________________________________________________________
This message has been checked for all known viruses by the 
MessageLabs Virus Scanning Service.

This is a multi-part message in MIME format.

------=_NextPart_000_0014_01C21231.14A6FA20
Content-Type: text/plain;
	charset="us-ascii"
Content-Transfer-Encoding: 7bit

One other great thing about XML is that most software coming out nowadays
can read XML, i.e Office XP is XML based, meaning that you can take an XML
document and put it into Excel and all will be happy days.

But I would still keep my money on using a database package such as Access
or SQL Server, as I can always load the information from that DB into a
DataSet, and convert that DataSet into an XML document. ASP.NET has built in
functionality for this which makes it a breeze!!

Greg

  -----Original Message-----
  From: Michael [mailto:mlang@m...]
  Sent: 10 June 2002 10:14
  To: ASP+
  Subject: [aspx] RE: why XML?



  It is rare that you would use it as a means of persisting data.  I have
only used it for that purpose when I had a small amount of data that I
wanted to be readable and editable from a text editor.

  Normally XML would be used as a means of interchanging data between
loosely coupled systems e.g in a hetrogenous environment you may wish to
communicate data from your MS system to another non-MS system suvh as unix.

  It can inefficient to use XML as your means of storing data especially
when you have large amounts of it.

  For those wishing to have the benefits of SQL database along with the
flexibility of XML you can use Datasets to easily work between the two
sources.


   -----Original Message-----
  From: sriram c [mailto:cpavan@w...]
  Sent: Tuesday, 11 June 2002 1:54 PM
  To: ASP+
  Subject: [aspx] why XML?


hi,
 I have simple application provider type of application where my server's
database is MS access type. I just cant find any use of using a complicated
XML
database.
can any one tell me unless i have a distributed application ..why should i
update to an XML d.base ,if at all?Is it a must in .NET to use XML d_base?

thankx in advance
sriram




------------------------------------------------------------
WWW.COM - Where the Web Begins! http://www.www.com


  --- Change your mail options at http://p2p.wrox.com/manager.asp or to
unsubscribe send a blank email to 

This is a multi-part message in MIME format.

------=_NextPart_000_001A_01C211E8.A8514B20
Content-Type: text/plain;
	charset="iso-8859-1"
Content-Transfer-Encoding: quoted-printable

I would add too that XML was not intended to serve as *the* datastore 
for dynamic applications.  You have the same age-long problems with an 
XML document that you did/do have with ordinary text files.  Those 
problems range from file locking issues when dealing with concurrency 
(what happens when 10 people want to update the XML file at the same 
time?), overall performance of having to parse a file node by node to 
find information (as opposed to indexing and hashing algorythms that 
happen behind the scenes), and security (who can access what 
tables/columns of a particular data set?).

Relational databases are and always will be the best way to handle 
relational data in a concurrent evironment.  Why?  They were designed to 
handle the above mentioned problems (and more!).  XML on the other hand 
was designed to be a data transport; getting disparate systems to speak 
to each other using a common protocol whose standards allowed for human 
readability.

Chris






  ----- Original Message -----
  From: Greg Quinn
  To: ASP+
  Sent: Wednesday, June 12, 2002 4:49 PM
  Subject: [aspx] RE: why XML?


  One other great thing about XML is that most software coming out 
nowadays can read XML, i.e Office XP is XML based, meaning that you can 
take an XML document and put it into Excel and all will be happy days.

  But I would still keep my money on using a database package such as 
Access or SQL Server, as I can always load the information from that DB 
into a DataSet, and convert that DataSet into an XML document. ASP.NET 
has built in functionality for this which makes it a breeze!!

  Greg

    -----Original Message-----
    From: Michael [mailto:mlang@m...]
    Sent: 10 June 2002 10:14
    To: ASP+
    Subject: [aspx] RE: why XML?



    It is rare that you would use it as a means of persisting data.  I 
have only used it for that purpose when I had a small amount of data 
that I wanted to be readable and editable from a text editor.

    Normally XML would be used as a means of interchanging data between 
loosely coupled systems e.g in a hetrogenous environment you may wish to 
communicate data from your MS system to another non-MS system suvh as 
unix.

    It can inefficient to use XML as your means of storing data 
especially when you have large amounts of it.

    For those wishing to have the benefits of SQL database along with 
the flexibility of XML you can use Datasets to easily work between the 
two sources.


     -----Original Message-----
    From: sriram c [mailto:cpavan@w...]
    Sent: Tuesday, 11 June 2002 1:54 PM
    To: ASP+
    Subject: [aspx] why XML?


hi,
 I have simple application provider type of application where my 
server's
database is MS access type. I just cant find any use of using a 
complicated XML
database.
can any one tell me unless i have a distributed application ..why should 
i
update to an XML d.base ,if at all?Is it a must in .NET to use XML 
d_base?

thankx in advance
sriram




------------------------------------------------------------
WWW.COM - Where the Web Begins! http://www.www.com

      
    --- 
  --- Change your mail options at http://p2p.wrox.com/manager.asp or to 
unsubscribe send a blank email to