If you’ve read my simple assessment of SQL Server’s In-Memory OLTP tables on Simple-Talk and have decided to implement them, we’re in a position to support your move. Redgate SQL Compare can help you compare two databases that have In-Memory objects, the tables, their indexes and any natively compiled procedures, and generate the appropriate scripts.
In the SQL Compare project below, for example, I’m comparing the new WideWorldImporters sample database that has In-Memory tables, and a test database on my server:
If I run a compare between these databases, a number of differences come up. You can select the specific objects, in this case tables, that you want to migrate. Selecting one of the tables for migration, you can see that the script shows the table will be created using In-Memory commands:
You can then deploy these objects using SQL Compare and everything will work fine, assuming you’ve set up the second database to support In-Memory tables. However, if you’ve not done this, we will stop the deployment:
This is to ensure your scripts will run successfully to deploy the In-Memory objects in question. You’ll also note we deal with how transactions have to work with In-Memory tables. Not only do we support the In-Memory functionality – we continue to offer guidance and assistance in your implementation of the new functionality.
To see SQL Compare in action, comparing and deploying In-Memory tables, take a look at this short walkthrough video
In short, when you’re ready for In-Memory OLTP behaviors, SQL Compare wil be there to help. We support the objects and data types and we have checks in place to help ensure your success when moving In-Memory objects between databases using SQL Compare.
Try it now free or ‘Check for Updates’ under the Help menu in-product to make sure you’re on the latest version.
Was this article helpful?