sql-server-2019

问题 Good morning, My first question is how to determine if tables created in MS SQL Server are memory optimized. I have some tables and I don't remember if some of them I created in-memory optimized or not. Many thanks for answers. 回答1: To riff off of another answer here, here's a way to get the status for all tables in your database: select name, OBJECTPROPERTY(object_id,'TableIsMemoryOptimized') from sys.tables; Similarly, if you want just the in-memory ones, you could do: select name from sys

问题 According to this link, SQL Server machine learning service's highest R version is 3.3. Does anyone know when one can upgrade to version 3.5 or later? Or is my only option to switch to sql server 2019? Thanks. 回答1: Well cs0815, let's take a look. According to your post, you tagged this with sql-server-2017, so I'll be basing this on that version. After reading through your link and this one, I was thinking there might be two options: Hack a new version of R into the R-Services module of SQL

问题 According to this link, SQL Server machine learning service's highest R version is 3.3. Does anyone know when one can upgrade to version 3.5 or later? Or is my only option to switch to sql server 2019? Thanks. 回答1: Well cs0815, let's take a look. According to your post, you tagged this with sql-server-2017, so I'll be basing this on that version. After reading through your link and this one, I was thinking there might be two options: Hack a new version of R into the R-Services module of SQL

问题 Getting an error below when restoring a AdventureWorks2017 database within a docker container. Running SQL Server 2019 CTP 2.0 (mcr.microsoft.com/mssql/server:vNext-CTP2.0-ubuntu) Both backup and target data volume are persisted. No problems creating new database. Checked the paths and they are correct. Do not have any problems when restoring using 2017-latest docker image. Anybody else have this issue with 2019-CTP2, workarounds? Msg 3634, Level 16, State 1, Line 7 The operating system

问题 Getting an error below when restoring a AdventureWorks2017 database within a docker container. Running SQL Server 2019 CTP 2.0 (mcr.microsoft.com/mssql/server:vNext-CTP2.0-ubuntu) Both backup and target data volume are persisted. No problems creating new database. Checked the paths and they are correct. Do not have any problems when restoring using 2017-latest docker image. Anybody else have this issue with 2019-CTP2, workarounds? Msg 3634, Level 16, State 1, Line 7 The operating system

来源： https://stackoverflow.com/questions/64247725/use-a-common-field-in-two-tables-with-xml-in-sql-server

来源： https://stackoverflow.com/questions/64247725/use-a-common-field-in-two-tables-with-xml-in-sql-server

来源： https://stackoverflow.com/questions/64548757/attempted-to-perform-an-unauthorized-operation-when-executing-sql-server-2019-se

来源： https://stackoverflow.com/questions/64424626/unpack-all-arrays-in-a-json-column-sql-server-2019

来源： https://stackoverflow.com/questions/62472377/how-can-i-make-sql-server-2019-pretend-that-a-stored-proc-is-in-progress