Best db for in C# and later C++

You question is vague and useless as stated.

What are your goals with the database? What use cases are you expecting? What kind of a load are you expecting? What operating systems are you expecting to be deploying to?

Goals:

• Save user data
  
• Save prices (Requested from another server that's of me.)
  
• ..
  
  Cases: How do you mean?
  Load: 1 man - 5 men (It's a personal app for friends.)
  OS: Windows for testing, Linux if it's published.

MySQL, PostgreSQL, SQLite, Binary Serialization, Xml Serialization.


Take your pick, you can access all of them from C# or C++.

Thanks for the fast answer! But 1 more question: what's the best UI for MySQL? (Except PhpMyAdmin, I got bad experience with that one.)

(PS. Sorry if my gram. and voc. isn't correct at all, I'm trying to do my best but I'm young and Dutch.)

To administer databases, you need to learn command-line SQL. There is no way around it -- without doing that, you will run into dead ends on all the various SQL databases. I think SQL Server (the Microsoft one) is the one that lets you get the furthest before needing the command line, though, so if that's a priority, I would choose that.

Another option, for the small application you're suggesting, is to simply use the file system. Store the data you need in files. Process all the requests through a single thread, to avoid race conditions. Write a new file on disk, and then remove the old file and rename the new file to the old name, to "commit" operations.

No, because they all need to access that data..

SQL Server Express 2012.

No, because they all need to access that data..

My suggestion was to store data in a file on the server. Each client connects to the server and sends requests. The server stores its data in files after processing requests.

[quote name='RobinVdB' timestamp='1337698651' post='4942224']
No, because they all need to access that data..

My suggestion was to store data in a file on the server. Each client connects to the server and sends requests. The server stores its data in files after processing requests.
[/quote]
I can try that.

SQL Server Express 2012.

Thanks

Shameless plug:

If you have found any of the posts helpful, please show your appreciation by clicking the up arrow on any of the posts

If you go the MySQL route then MySQL Workbench is a pretty good GUI app for manipulating databases. Other then the initial database install you could almost probably get away with never having to touch the command line again.

Don't think there are any kind of GUI apps for it but depending on how you needed to store your info MongoDB might be another option.