After upgrade to 2016 can't import Azure V12 bacpac
We've recently upgraded our development server from 2014 to 2016. We had already been using some 2016/Azure V12 functionalities on production in certain views.
Now that we want to restore a recently exported bacpac file from our production database on Azure, it fails with the following message:
Perhaps the internal DB engine is still running on 2014? I couldn't find anything concrete about it on Google.
The documentation on STRING_AGG() indicates the feature is available in Azure SQL Database and SQL Server 2017, but not SQL Server 2016. You need to use only common features if you want to import BACPACs between different versions.
If this was working before the on-prem upgrade, I suspect that was before the proc with STRING_AGG() was created or changed.
- Math.Sin() gives incorrect value
- How to run my python script when the sunOS is start booting
- Express-session: not resetting cookie expiration on each request
- Getting a stack overflow exception when normalizing a vector
- Edit default summary function in R gives error for multiple variables
- What was a For loop? Why isn't it needed in R?
- How to use download button in shiny and save results in various formats (csv, texte, pdf, spss...)?
- Why are there two assignment operators, `<-` and `->` in R?
- lm()$assign: what is it?
- How to get the value of list(...) in R and S functions
- Design matrix for MLM from library(lme4) with fixed and random effects
- how to generate elements not included in my sample
- Create a matrix with gradually changing values without a for loop
- Emacs ESS and S-plus ( S+ ) 8.1 compatability
- How to lag date-index in a time-series in R?
- Nonlinear regression in R / S
- Calling R from S-Plus?