March 27, 2015 at 3:57 pm
Hello,
I am just researching this new In-Memory OLTP feature and have some questions.
1. Is there going to be a performance hit on the live servers while we are doing the AMR analysis and when we do the actual migration for tables and stored procedures? If so what is the piece that will be affected? Memory? cpu? I/O?
2. During the conversion of the tables to new In-Memory tables will the old tables be locked or suffer performance during the actual table migration?
3. I have read an article on the actual migration process and it says to rename the table to a different name is that required? How are we going to switch users from the old table to the new In-Memory table with out any down time or performance hit?
4. I ask the same question (1. and 2. above), but for stored procedures?
5. Do we need to restart SQL service and SQL Agent service after the migration?
Appreciate the help.
March 30, 2015 at 2:57 am
It's not a migration. It's not a 'alter table set in-memory'. You create new tables which are in-memory and you copy the data from the old tables to the new tables. Hence you really need downtime to do it.
I suspect the fastest way would be
Create new in-memory table
Insert into in-memory table from disk-based table
Drop table disk-based table
Rename in-memory table to the same name that the old table had and hope you did sufficient testing to ensure that there are no problems
Gail Shaw
Microsoft Certified Master: SQL Server, MVP, M.Sc (Comp Sci)
SQL In The Wild: Discussions on DB performance with occasional diversions into recoverability
March 30, 2015 at 10:34 am
Cool and I'm assuming you have to restart sql services?
Viewing 3 posts - 1 through 2 (of 2 total)
You must be logged in to reply to this topic. Login to reply