{"action":"closed","issue":{"url":"https://api.github.com/repos/Microsoft/sql-server-samples/issues/434","repository_url":"https://api.github.com/repos/Microsoft/sql-server-samples","labels_url":"https://api.github.com/repos/Microsoft/sql-server-samples/issues/434/labels{/name}","comments_url":"https://api.github.com/repos/Microsoft/sql-server-samples/issues/434/comments","events_url":"https://api.github.com/repos/Microsoft/sql-server-samples/issues/434/events","html_url":"https://github.com/Microsoft/sql-server-samples/issues/434","id":356023069,"node_id":"MDU6SXNzdWUzNTYwMjMwNjk=","number":434,"title":"Publishing database as in-memory without disk-table to migrate","user":{"login":"XeroXiTe","id":3824689,"node_id":"MDQ6VXNlcjM4MjQ2ODk=","avatar_url":"https://avatars0.githubusercontent.com/u/3824689?v=4","gravatar_id":"","url":"https://api.github.com/users/XeroXiTe","html_url":"https://github.com/XeroXiTe","followers_url":"https://api.github.com/users/XeroXiTe/followers","following_url":"https://api.github.com/users/XeroXiTe/following{/other_user}","gists_url":"https://api.github.com/users/XeroXiTe/gists{/gist_id}","starred_url":"https://api.github.com/users/XeroXiTe/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/XeroXiTe/subscriptions","organizations_url":"https://api.github.com/users/XeroXiTe/orgs","repos_url":"https://api.github.com/users/XeroXiTe/repos","events_url":"https://api.github.com/users/XeroXiTe/events{/privacy}","received_events_url":"https://api.github.com/users/XeroXiTe/received_events","type":"User","site_admin":false},"labels":[],"state":"closed","locked":false,"assignee":null,"assignees":[],"milestone":null,"comments":1,"created_at":"2018-08-31T15:18:57Z","updated_at":"2018-09-10T08:18:02Z","closed_at":"2018-09-10T08:18:01Z","author_association":"NONE","body":"Hi, \r\nI'm trying to setup a SQL database project that would:\r\n1. Create a database\r\n2. Create a in-memory table (either for SQL Server or Azure SQL Server)\r\n\r\nHowever from the samples provided here, I get is that you first of all need to publish disk-table, then migrate the schema in the project to memory optimised table and publish it again. This creates a problem for me since I don't want to be publishing database multiple times, especially if multiple environments are involved.\r\n\r\nThings I've tried:\r\n1. Creating a disk-table in pre deployment script and then just have memory optimised table schema. This would throw exception that Object already exists, because pre deployment step already creates a table.\r\n2. Creating a disk-table normally, but then have a memory optimised table creation in post deployment. That didn't work either.\r\n3. Just have a memory optimised schema on a table itself. This would start complaining about AUTO_CLOSE not being supported because of Filegroup creation when running it against SQL Server. Haven't tried it against Azure SQL, but as I mentioned before I wanted this to work on either without manual intervention.\r\n\r\nI've used sample database from: [Ticket-reservations](https://github.com/Microsoft/sql-server-samples/tree/master/samples/features/in-memory/ticket-reservations)\r\n\r\nAny ideas or suggestions would be appreciated."}}
{"actor":{"display_login":"XeroXiTe"}}