Database design questions

[Saksida Bojan]

Here i have a few question: Is Xml Good for large databases? Shoud i use XmlDocument or XmlReader and XmlWriter? If i chose XmlReader and XmlWriter how would i manage to quickly delete data? I am developing OpenSource application, that uses plugin based database. Is it good to connect to remote server(MySQL) using .NET Connector? I Also thinking of creating server app that will be on server betwen mysql and Client. Is TCP good protocol or shoud i consider UDP. Currently i am reading about TCP and i am thinking if i should send XML data through TCP. Does this data need to be encoded (Base64) or encrypted (AES)?

[Mycroft Holmes]

Probably belongs in the Design and Architecture[^] forum! xml is NOT good for large databases, xml is a descriptive platform it is NOT a database. Some have used it for minute data requirements where it may be valid but certainly not for any valume. This is dependant on winforms/web application (among other things) you do not say. We use OLEDB (SQL) connections for winforms The server app is probably a Web Service - there is plenty of articles and samples around for these. XML vs Binary transport layer is an old and well used argument, you need to do some research to determine which will suit your needs best. Encryption is dependant on your data sensitivity, general info may not require encryption where authentication almost certainly does.

[Saksida Bojan]

Thank you for your anser. I didn't notice that forum, i won't post there that will create double post. As i have said i think using MySQL .NET connector (Witch clearly says i am using .NET Framework), not OLEDB and i didn't start as web service only as windows service

[N a v a n e e t h]

Saksida Bojan wrote:

Is Xml Good for large databases?

What do you mean by that? Keeping all data in XML format? If yes, it is a bad idea.

Saksida Bojan wrote:

Shoud i use XmlDocument or XmlReader and XmlWriter?

I am not sure that these 3 classes can be compared as each of them serves different purpose. XmlDocument is an in-memory DOM representation of the XML and other two are used for reading and writing. If you want to persist the XML in memory and need to manipulate it(querying with XPath etc..), choose XmlDocument. XmlDocument can also make the data editing and writing easy. If you have a custom data structure that has to be created/persisted to XML, prefer XmlReader and XmlWriter.

Saksida Bojan wrote:

If i chose XmlReader and XmlWriter how would i manage to quickly delete data?

Use XmlDocument in such case and call its Save() method for writing to XML file.

Saksida Bojan wrote:

Is it good to connect to remote server(MySQL) using .NET Connector?

No - if it is a stand-alone application. Wrap the database access behind a web service/WCF.

Saksida Bojan wrote:

I Also thinking of creating server app that will be on server betwen mysql and Client. Is TCP good protocol or shoud i consider UDP. Currently i am reading about TCP and i am thinking if i should send XML data through TCP.

This is exactly what a WCF or web service layer does. WCF uses TCP communication and web services uses SOAP messages. :)

Navaneeth How to use google | Ask smart questions

[Saksida Bojan]

N a v a n e e t h wrote:

Saksida Bojan wrote: Is it good to connect to remote server(MySQL) using .NET Connector? No - if it is a stand-alone application. Wrap the database access behind a web service/WCF.

It is dll that has connector and uses socket to connect dirrectly to MySQL database. it is OpenSource and it does not require to install unlike it is with ODBC

N a v a n e e t h wrote:

This is exactly what a WCF or web service layer does. WCF uses TCP communication and web services uses SOAP messages.

I Don not know what WCF is, but i will look into it. What is diffrent by Windows Service and Web service? Can Windows Service uses protocol such as TCP or UDP? Thanks for the information, it realy helps

[N a v a n e e t h]

Saksida Bojan wrote:

What is diffrent by Windows Service and Web service?

Windows services are normal applications that runs all the time and controlled by a service manager. It needs to be installed using installutil utility. On the other hand, web services follow request/response architecture. It resided on a server and serves requests. Communication is done on XML format following SOAP protocol.

Saksida Bojan wrote:

Can Windows Service uses protocol such as TCP or UDP?

Yes.

Navaneeth How to use google | Ask smart questions