how to create an "offline" database?

Question

okay, can somebody please tell me how to build a database OFFLINE, without using an actual server?

i am planning on using an SQL database, and was told Access cannot handle large chunks of data (i'm working on an older PC with Win XP, and no internet).

if Access will work okay, and can be converted to an SQL database to upload to an ONLINE server (as opposed to a "local" one), could somebody fill me in on it?

10 points to the most detailed/helpful answer...

Answer 1

depends on what you actully need to build , but as i understood , you want to build a database using sql , with no need to be published on the internet or to be on a server , u can build a "local" database using MySQL 5.5 command line client



you can download it from here : http://www.mysql.com/downloads/mysql/



and when u do so , open the command line client and start using SQL to build your database.



additional details answer :



OK , when your are finished creating the database and inserting the data you want to insert in its tables , u can export the database using your computer (check MySQL reference on their website for how to export databases using MySQL) and import it using any computer / server that has a database management system installed on .



about database being only searchable , not editable by users , this is possible by any DBMS , mysql , sqlite , MSSQL , even access , its about permissions , the database administrator is the one who assigns permissions and creates views of the database tables as needed.



don't forget to chose the right engine for your database , if you have many foreign keys and need to use transactions , you would need to use innodb , which is the default engine that MySQL 5.5 has.

Answer 2

Microsoft SQL server is also a choice. You can install it on your XP box (assuming your PC isn't so old that it can't handle the minimum system requirements, but most XP boxes should be OK. If you can upgrade the amount of memory installed, that would be a worthwhile investment).



Create the database locally, then when it's time to move it to the real server, you can export it, then import it. (It's been a few years since I worked with MS-SQL, so I don't remember the exact details, but it isn't very hard, as I recall. Google should be able to tell you the steps).



As long as it remains non-user editable, then you can repeat the export/import step as many times as you need. It gets much harder to manage if someone is also changing the database on the actual server. But it sounds like you don't have that issue.

Answer 3

The heart of the bill is there. Newborn screening is critical for early detection and long term viability of children born with inborn errors in metabolism and other detectable genetic diseases. So expanding the program is pretty much a good thing. However, I would agree with Dr. Paul in that any statistics obtained from program need to be collected anonymously and that the privacy rights and patient records of any child that comes up positive for a genetic disorder need to be protected and should never be released w/o the parent's consent. Good question. The problem comes into play in that refusing the newborn screening is similar to refusing lifesaving medical care for your child. If your child happens to have a metabolic disorder that could be picked up with a $5 genetic test that you refuse, your child could suffer irreparable brain damage from that disorder or ends up dying. And since the child can't accept or deny treatment of its own accord the state steps in. This is why I believe you can't refuse the genetic tests. I believe this only applies to the state/federal standards though. Some hospitals run even more disorders and I believe you can still refuse these since its on a hospital by hospital basis. Should you be able to maintain all semblance of privacy concerning the results of these tests? Absolutely.