Spludlow Mame Web Header

Spludlow MAME - MAME Database Downloads


MAME: 0.225 - Released: 2020-09-29T12:40:38 - Machines: 42816 - rom: 317359 - disk: 1085 - Lists: 611 - Software: 126197 - rom: 207332 - disk: 9835

Downloads

Request a MAME database product



(Optional) Please let us know what you're doing with the data set, out of interest.


Please enter the 3 digit code then click the button

MAME Database Downloads Details

 

MAME databases in Microsoft Access

Microsoft Access is an excellent way of quickly familiarizing yourself with any dataset. It also makes building queries very simple and will generate the SQL that you can use it elsewhere (without having to write it yourself).

You can use it stand alone with the data stored in the .accdb or as a front end, using linked tables, to connect to a database server (with ODBC drivers).

The MAME data sets are available in Microsoft Access format.

 

MAME databases in MySQL Dump

The MAME data sets are available in MySQL Dump format.

To load the data on the server:

·         Start MySQL Workbench and connect to a server instance

·         Create an empty schema (Navigator -> Schemas -> Right click -> Create schema…)

·         Run the SQL script against the newly created schema (File menu -> Run SQL Script… -> Select SQL File -> Change Default Schema)

To create a database diagram:

·         Start MySQL Workbench and connect to a server instance

·         Database Menu -> Reverse engineer…

·         Click through with next selecting your schema

 

MAME Databases in SQL Server BAK

The MAME data sets are available in Microsoft SQL Server BAK format.

Restoring from an SQL Server BAK file

NOTE: The BAK was created on version 2017 (14) you will not be able to restore to previous server versions.

Restoring a SQL BAK from another machine is not straightforward, but when you have figured it out it is very quick.

First of all, make sure you understand it’s the server not the client that is accessing the BAK file. If your server is on another machine (not what you are running SSMS on) then the file needs to be on the server. Also, the server process is running as a different user than your user so even on the same machine, due to filesystem permissions, the server still can’t access files for example on your desktop.

Create a work folder

This should be created on the server machine. The SQL Server user will need to be given permission.

The user name is “NT SERVICE\MSSQLSERVER” for a default instance, or “NT SERVICE\MSSQL$InstanceName” for named instance. Give it full control.

Restoring a BAK file

NOTE: All values here a on a default installation, you will have to substitute values for your requirements.

·         “MyMameMachine” &” MyMameSoftware” are the target database names you require, they are also present as part of the target physical filenames.

·         “C:\Program Files\Microsoft SQL Server\MSSQL15.MSSQLSERVER\MSSQL\DATA\” is the path to the server datafiles, ensure you can browse to it and replace if required.

·         “C:\SQLBACKUP\MameMachine0.224.bak” is the source BAK file wherever you have it.

·         Don’t change “MameMachineTemp” &” MameSoftwareTemp” they are the logical names within the BAK.

Copy the BAK files to the work directory “C:\SQLBACKUP”.

Machine - Run on the master database:

RESTORE DATABASE [MyMameMachine] FROM DISK='C:\SQLBACKUP\MameMachine0.224.bak' WITH REPLACE,

MOVE 'MameMachineTemp' TO 'C:\Program Files\Microsoft SQL Server\MSSQL15.MSSQLSERVER\MSSQL\DATA\MyMameMachine.mdf',

MOVE 'MameMachineTemp_log' TO 'C:\Program Files\Microsoft SQL Server\MSSQL15.MSSQLSERVER\MSSQL\DATA\MyMameMachine_log.ldf';

 

Software - Run on the master database:

RESTORE DATABASE [MyMameSoftware] FROM DISK='C:\SQLBACKUP\MameSoftware0.224.bak' WITH REPLACE,

MOVE 'MameSoftwareTemp' TO 'C:\Program Files\Microsoft SQL Server\MSSQL15.MSSQLSERVER\MSSQL\DATA\MyMameSoftware.mdf',

MOVE 'MameSoftwareTemp_log' TO 'C:\Program Files\Microsoft SQL Server\MSSQL15.MSSQLSERVER\MSSQL\DATA\MyMameSoftware_log.ldf';

 

Set the dbo - database owner

Database need to have an owner user, if they don’t they will play up. Attempting to generate a diagram in SSMS won’t work for a start.

As the backup was made on another computer that user does not exist on the restore computer.

Run this on each both databases (Machine & Software) substitute your host or domain name and username:

sp_changedbowner 'HOSTORDOMAIN\Fred';

Fix the logical filenames (optional)

This step is not necessary, everything will work fine without it, it fixes the logical data filenames from what they are on the source computer to what you want them to be.

Machine - Run on the master database:

ALTER DATABASE [MyMameMachine] MODIFY FILE (NAME='MameMachineTemp', NEWNAME='MyMameMachine');

ALTER DATABASE [MyMameMachine] MODIFY FILE (NAME='MameMachineTemp_log', NEWNAME='MyMameMachine_log');

 

Software - Run on the master database:

ALTER DATABASE [MyMameSoftware] MODIFY FILE (NAME='MameSoftwareTemp', NEWNAME='MyMameSoftware');

ALTER DATABASE [MyMameSoftware] MODIFY FILE (NAME='MameSoftwareTemp_log', NEWNAME='MyMameSoftware_log');

 

Create a database diagram

In SSMS expand the database and right click on Database Diagrams.

 



Spludlow Mame Web Footer