6 ms·
So maybe this is not the answer you'll be happy with, but... Maybe it just looks more scary than it is. Do you really need to automate it? 2gb is not that larg
by viraptor 10y ago
So maybe this is not the answer you'll be happy with, but... Maybe it just looks more scary than it is. Do you really need to automate it?
2gb is not that large these days - set up a local MySQL and import it. 36 tables should be doable by hand very quickly if they have good naming. If they don't have good naming, it's not going to link them automatically anyway.
If you want some GUI that allows you to create quick and simple search forms, try libre office base
- SnowingXIV 10y agoIt's a .bak file and yeah manually doesn't seem too awful as I look through all the tables. I'm thinking first need to install SQL Server Management Studio and then restore the .bak from there and then I don't know what would be the best next steps.
- viraptor 10y agoCheck the schema - maybe some tables have foreign indexes already. Then try to link up obvious names - do you have a table users and columns named user_id somewhere else? Then if you still have disconnected tables, take a few sample rows and see what looks like identifiers / keys. You can join that column with another one in the database and see if they match up completely, or if one has IDs that the other one didn't. As you're doing this, write down comments about what the tables contain, so you can do sanity checks (do users really reference foos? does that make sense?) I'm assuming your question means you don't have access to the application for this database, or can't run it and sniff the queries from the network.