Netherlands: Software

Introductie van Micorosoft SQL Server 2016

Issue link: http://hub-nl.insight.com/i/692679

Contents of this Issue

Navigation

Page 17 of 212

7 C H A P T E R 1 | Faster queries A new feature in SSMS is the ability to generate migration checklists. To do this, right-click a database in Object Explorer, point to Tasks, and then select Generate In-Memory OLTP Migration Checklists. This step launches a wizard that displays a welcome page. On the second page of the wizard, you specify a location in which to save the checklist and whether to generate a checklist for all tables and stored procedures in the database or for a specific list that you define. After you make this selection, the next page of the wizard includes a Script PowerShell Commands button and a Finish button. If you select the Script PowerShell Commands button, a text file opens to display the following command: Save-SqlMigrationReport -Server '' -Database 'AdventureWorks' -FolderPath 'C:\Users\\Documents\' When you click the Finish button, the wizard begins to generate a separate checklist for each table and stored procedure specified in the wizard. The status of each checklist is displayed in the table so that you can easily see whether any failed. After the wizard completes the checklists, you can find them as HTML files in the Stored Procedures, Tables, or User Defined Functions folders in the output path that you configured in the wizard. An example of a migration checklist for a table is shown in Figure 1-2. Figure 1-2: Checklist for migrating a table to In-memory OLTP. As an alternative to using SSMS to generate the checklists, you can use SQL Server PowerShell. In Object Explorer, right-click a database, and then click Start PowerShell. In the SQL Server PowerShell command window, enter the following command: Save-SqlMigrationReport -FolderPath 'C:\Users\\Documents\' Notice that this is similar to the command generated by the migration checklist wizard, but it omits the server and database arguments because the SQL Server PowerShell command window connects directly to the correct database when you open it. If you prefer, you can use a Windows PowerShell command window (open it with administrator permissions), in which case you must enter and execute the commands shown in Example 1-5. The second command produces a migration checklist for all tables and stored procedures in the database at the location you specify in the FolderPath argument. The object that you reference in the third command must be either a table or a stored procedure. Use this command when you want to generate a checklist for one object at a time.

Articles in this issue

Archives of this issue

view archives of Netherlands: Software - Introductie van Micorosoft SQL Server 2016