If using an in-memory table in SQL Server 2016, can I define a column in that table as a foreign key from a non in-memory (or disk bound) table? I know that the foreign key does need to be the primary key of the referenced table.
I'm just wondering about the limitations and reliability of in-memory tables and how well they work with disk bound tables in SQL Server 2016.