A Database mockup is a copy of the objects and rows that are affected by the DMLs in your SQL Script.  Mockups are not copies of the entire database nor the entire table.  If your DML only affects 1 record in 1 table, only 1 record and only 1 table will be created in your "Simulated Database".  SQL Simulator can create 2 types of Mockups.

• Preview Mockups
• Postview Mockups

Please click here to read the technical overview of how SQL Simulator works.

Preview Mockups show you the objects and rows affected by your SQL script before it is executed against the database.  For example lets say I have the following SQL:

​update color
set color_name = 'yellow'
where color_id = 1;

You process this SQL in the SQL Simulator and have it generate a preview mockup.  This is the result you will see in the simulated database

You may be thinking shouldn't the color_name = 'yellow'.  The reason you see 'black' is because the simulator is showing you the current value as it exists in production.  Your script has not been run yet.  These are the objects and rows affected by your script.  FYI your production database is not updated.

Preview Mockups show you the objects and rows affected by your SQL script after it is executed against the database.  For example lets say I have the following SQL:

​update color
set color_name = 'yellow'
where color_id = 1;

You process this SQL in the SQL Simulator and have it generate a postview mockup .  This is the result you will see in the simulated database

The value in color_name = 'yellow' this time.  This is because the Simulator is showing you what the value of your column would be after your sql script has run.  FYI your production database was not updated.

The above examples are fairly simple and straight forward.  However you can do more complex scripts(Especially Foreign Keys).  Feel free to try more complex SQL Scripts with SQL Simulator.    You can give it a try for free by clicking here.

According to chat gpt a dry run :

"Refers to a rehearsal or practice session conducted in a simulated or controlled environment to test the execution of a process, system, or event without actually implementing it in its full operational capacity. It involves going through the motions and steps of a particular activity, such as a presentation, procedure, or software implementation, to identify potential issues, assess readiness, and familiarize participants with the expected workflow. Dry runs are typically employed to uncover and rectify any flaws, ambiguities, or inefficiencies before the actual implementation or live performance takes place, allowing for adjustments and improvements to be made, thereby enhancing the overall outcome and reducing the likelihood of errors or disruptions."

To verify if your SQL scripts will execute and that those SQL scripts are doing what you think they will do.

SQL Simulator makes performing dry runs easy with just the click of a button.

The setup process can take as little as 5 minutes.  Here is what you need

1. Download the software
2. Unzip the software(There is no installer)
3. Create a blank/empty schema in a non production database
4. Configure data sources

A "hello world" tutorial can be found by clicking here

It is similar in concept to Redgate SQL Clone or Windocs.  If you are not familiar with these tools they make clones of your database.  The key difference with SQL Simulator is, it only makes a clone of the database objects affected by your sql script not the entire database.  Nor does it copy the entire table (if your sql has  where clauses).  Once those database objects have been cloned, SQL Simulator then executes your script against the cloned database it created.

For a more in-depth technical overview click here

Here you go