How can I upgrade R version in SQL server 2017? - r

I want to use silhouette_kproto function from clustmixType library of R in SQL Server 2017.But it not working for current version of R. Can I just upgrade the R version to be used in SQL server?

You cannot upgrade the R version to anything higher than 3.4.3 for SQL Server 2017, as per what #Ralf Stubner says in his comment.
This is related to the other components that make part of SQL Server Machine Learning Services, (SqlSatellite, BxlServer, etc.).
To see how to upgrade look here, (link to MS docs).

Related

Is there an ODBC Driver for MariaDB in IBM PASE?

As part of the open-source software on PASE for i, MariaDB is available in the ibm repository. However, it seems like the MariaDB Connector/ODBC is not available.
Following the Building MariaDB Connector/ODBC From the Git Repository instructions does not work, since it appears that PASE is not supported. Forking it and modifying the source + build toolchain to work in PASE seems like a potential (but unattractive) option.
Is there a MySQL ODBC driver that can be used instead? Have I missed an available package? I also noticed that Zend / Seiden / etc have discussed using PHP with MySQL / MariaDB on PASE for i, how is PHP connecting to MariaDB in that case?
IBM does not currently provide an ODBC interface for connecting to MariaDB. Most high level languages provide a MySQL/MariaDB interface which does not require the client libraries (eg. PyMySQL).

Does Flyway Community version support Oracle 19.7?

Does flyway community version support Oracle 19c? From this URL: https://flywaydb.org/documentation/database/oracle, it is up to 19.3. My oracle database is 19.7. I am not very familiar with oracle database versions.
Any version support oracle 19.7 at all?
Thanks!
Assuming no breaking changes have appeared in Oracle 19.7, then yes, we just have not formally tested it yet. If you try, you will get a warning to this effect in the log but Flyway will function as normal. I'll update the tests and remove this warning for the next patch version.

Error connecting to mongoDB using Mongolite

I'm having issues connecting to my MongoDB via Mongolite, and I'm not sure if it is an issue on my side, or if I need to use a different package to connect to the database. Please keep in mind that I cannot change the software being run by the MongoDB server, and I am a novice when it comes to all of this, so it could just be a silly error on my part.
I've run the following code:
m <- mongo(collection = "test", url="mongodb://22.92.59.149:27017")
As far as I can tell from the Mongolite tutorial (https://jeroen.github.io/mongolite/), this is the correct syntax to connect to the database, but I'm not 100% sure. Regardless, I get the following error:
Error: Server at 22.92.59.149:27017 reports wire version 2,
but this version of libmongoc requires at least 3 (MongoDB 3.0)
From what I can tell, this means that mongolite won't work with my database. If that is the case, what other package should I try to use to connect, or if it is not the issue what am I doing wrong?
Thanks in advance!
As the message says, there is a mismatch between versions of the client and the server.
More precisely, mongolite relies on a more general driver written in C, libmongoc, and it seems the version automatically installed by the install.packages("mongolite") statement is too recent towards the server's version.
If you can't change anything server-side, maybe you could try to manually install an older version of libmongoc before installing mongolite, but I'm not confident about the compatibility with that R package afterwards.
Maybe you can use RMongo, an older and archived package to interact with Mongo in R, but I'm afraid what you're going to develop won't be stable in further R versions.
I'd rather recommend you to look at the problem server side.

SQL Server 2016 integration with R Services

While trying to integrate R Studio with SQL Server 2016 I am getting following error:
Unable to launch runtime for 'R' script. Please check the configuration of the 'R' runtime.
As suggested on different sites it is advised to install "%programfiles%\RRO\RRO-3.2.2-for-RRE-7.5.0\R-3.2.2\library\RevoScaleR\rxLibs\x64\RegisterRExt.exe" /install.
But I have already installed R studio and not able to find the path specified.
R Services for SQL 2016 is a new offering from Microsoft - who purchased Revolution Analytics about a year ago. This is the first major result of that.
SQL Server 2016 is in (CTP - community technical preview), so not really finished (although you can download and use a version that will expire after about 6 months). Also a lot of the docs are incomplete and there are probably a fair amount of bugs. However it has been long announced that it will include "R Services for SQL 2016", which is based on the Revolution R Engine. In order to use that you have to
Install SQL Server 2016 CTP as usual.
Install the "Advanced Analytics Extensions" from the setup.exe program (see https://msdn.microsoft.com/en-us/library/mt590808.aspx)
Obtain the appropriate RevoScaleR packages (there are two) and install them, one your client, and one on the machine running SQL 2016. They are described here: https://msdn.microsoft.com/en-us/library/mt604883.aspx
Then to test it you can follow the instructions here: https://msdn.microsoft.com/en-us/library/mt590808.aspx
Good luck with it, but remember it is still in pre-release development and testing, so problems are to be expected.

Migration from legacy version to newer version or MySQL

I recently dug up a very old SQL Anywhere database. I have it installed and it kind of works, its only the distributed side of the data, so everything's running via dbeng50 and ODBC.
I would like to migrate this data to MySQL. Is there a way to do this? I attempted to view the data using an ODBC tool but I kept getting error messages saying the ODBC driver doesn't support the version of ODBC behavior.
I guess the database is too old (it's from 1997) - that put's at it SQL Anywhere version 5.
Its also difficult to find the old SQL tools that would help me access these.
Is it possible to use the .db file with a newer version?
Any help or guidance at all would be appreciated.

Resources