, ResourceID , [Date] , Minutes , LastModifiedByID , LastModifiedDate ) VALUES( @BookingID , @ResourceID , @Date , ISNULL(@Hours, 0) * 60 , @LoggedInUserID , GETUTCDATE() ) END ELSE BEGIN SET @ErrNo = 51104 Goto Crash END Indices Migration When creating memory optimized tables, no UNIQUE indexes other than the PRIMARY KEY are allowed. Also, range indexes are not available in CTP 1 (available in CTP2). As a result, all indices are converted to NON CLUSTERED HASH indices. Read isolation issue READ_COMMITTED_SNAPSHOT is supported for memory-optimized tables with auto commit transaction and only if the query does not access any disk-based tables. When accessing a table from an explicit or implicit transaction that uses interpreted Transact-SQL, an isolation level table is required. Therefore, all dependent procedures must include WITH (SNAPSHOT). Post Migration Analysis The post migration analysis is done at two levels: 1) Read level 2) Write level. The procedures that have no dependencies on the memory optimized Schedule table show no improvement in performance. Of the five scenarios, the following procedures are dependent on the Schedule table and have improved performance: Bookings Procedure Resources Procedure Get Project Schedule Procedure Hekaton Read level performance: At the read level, Bookings procedure demonstrated 187% improvement in first run:
, ResourceID , [Date] , Minutes , LastModifiedByID , LastModifiedDate ) VALUES( @BookingID , @ResourceID , @Date , ISNULL(@Hours, 0) * 60 , @LoggedInUserID , GETUTCDATE() ) END ELSE BEGIN SET @ErrNo = 51104 Goto Crash END Indices Migration When creating memory optimized tables, no UNIQUE indexes other than the PRIMARY KEY are allowed. Also, range indexes are not available in CTP 1 (available in CTP2). As a result, all indices are converted to NON CLUSTERED HASH indices. Read isolation issue READ_COMMITTED_SNAPSHOT is supported for memory-optimized tables with auto commit transaction and only if the query does not access any disk-based tables. When accessing a table from an explicit or implicit transaction that uses interpreted Transact-SQL, an isolation level table is required. Therefore, all dependent procedures must include WITH (SNAPSHOT). Post Migration Analysis The post migration analysis is done at two levels: 1) Read level 2) Write level. The procedures that have no dependencies on the memory optimized Schedule table show no improvement in performance. Of the five scenarios, the following procedures are dependent on the Schedule table and have improved performance: Bookings Procedure Resources Procedure Get Project Schedule Procedure Hekaton Read level performance: At the read level, Bookings procedure demonstrated 187% improvement in first run: