|
-
Aug 19th, 2012, 01:00 AM
#1
Thread Starter
Hyperactive Member
Data
I've got a project I need to build and it will be distributed around a number of people who have different computer settings and software.
I need to access lots of information on countries and cities.
My issue is where to store this where i can index it, search it and update it if required.
SQL Server - would be the best option until I consider many of my users will not have it.
XML - will it be too slow? can I index it?
SQLite - what's it about, how robust and portable is it?
Are there any other options?
-
Aug 19th, 2012, 01:35 AM
#2
Re: Data
 Originally Posted by ubkra
I've got a project I need to build and it will be distributed around a number of people who have different computer settings and software.
I need to access lots of information on countries and cities.
My issue is where to store this where i can index it, search it and update it if required.
SQL Server - would be the best option until I consider many of my users will not have it.
XML - will it be too slow? can I index it?
SQLite - what's it about, how robust and portable is it?
Are there any other options?
Have you tried loading xml via DataSet.ReadXml and use work with the data this way then to save the data use DataSet.WriteXml.
-
Aug 19th, 2012, 02:24 AM
#3
Thread Starter
Hyperactive Member
Re: Data
the issue I have with XML is how can I reference/index nodes
For example, I'll have a city XML file. I'll have to also create a user XML file where I can write where orders are doing to, for example:
User1: city London or CityID 4114 or City Code LON.
This User entry will need to call information on London. Hence a database being the most suitable choice IF it was portable.
-
Aug 19th, 2012, 02:44 AM
#4
Re: Data
You wouldn't need multiple XML files. XML is hierarchical, so you could store an entire relational database with multiple tables and multiple relations between the tables in a single XML file. As suggested, the DataSet class has a method that will read such a file into a DataSet, just like you retrieved the data from a database. You can then edit the data as you like and call WriteXml to write the new data back out to a file. The simplest way to create such an XML file in the first place is to create a DataSet with the appropriate schema in code and then call WriteXml on it.
If the amount of data is too large then XML may be a bit inefficient. In that case a database would be the way to go. If all your users are on a network and can access one database then SQL Server would be a good option. If your users are unrelated then you could have them install SQL Server Express automatically as part of your app's installation. You could also use Access, as everyone has the components required to use MDB files as part of Windows. You could use SQL Server CE, which can be installed or you can deploy a library or two with your app. SQLite can also be used by deploying a library with your app. I've never used it but it's apparently quite quick and easy to use.
Posting Permissions
- You may not post new threads
- You may not post replies
- You may not post attachments
- You may not edit your posts
-
Forum Rules
|
Click Here to Expand Forum to Full Width
|