Newbie MySQL question

[The_J]

I am pretty new to SQL. Ive been writing a program that accesses a MySQL database on a server computer from another computer here to do all of its work (stores and retrieves everything on/from the remote database), just to learn how to get it all to work.

Now that I have that learning part done, I need to change the program to have it connect to the remote computer only to get one database update (for selectable items), but keep everything else (names, phone numbers, selected items, etc.) on a private database stored on the users computer that never has anything to do with the internet. I have no idea what the correct term for this kind of private database is, how it works or if that aspect of it is even possible using MySQL. Teamspeak, as I understand, uses a type of SQL service (sqlite I believe, though I saw on their boards someone got it to work with MySQL) where it stores names that have logged in on a local database.

Does anyone have any info or a link to a guide on how I would go about setting up such a database? Or even the name of this kind of database would help immensely. Thanks!

 

[MrPaul]

sqlite vs MySql

Ive not used MySQL or sqlite that much, and never within a .Net application, but here goes...

A database which resides on the same machine the application is running on is just a local database, and is essentially the same as a remote database only stored locally. You will therefore need a database engine installed locally, either as part of the application itself (sqlite), or a service (MySQL). As far as I know there is no special name for a local database.

If using sqlite, there is an ADO.Net provider for it called System.Data.SQLite. The big advantage of this approach is that the end user does not need to install (and configure) an RDBMS such as MySQL, as the entire database engine is contained within the sqlite package.

If using MySQL, you use a connection string exactly as with a remote database server - the application does not care whether the database server is local or remote. The advantage of this approach is that the code to access the local database will be pretty much identical to any code used to access the remote one.

Personally, I would suggest checking out System.Data.SQLite mentioned above as it appears the most appropriate solution.

Hope this provides some help. Good luck