We are planning to use freetds 1.1.4 in our organisation to connect to SQL Server 2017 using Perl and C++.
We saw a compatiblity chart but it doesn't have any info for SQL Server 2017. Could you please let us know whether we can use 1.1.4 for Microsoft SQL Server 2017. Please do reply
Below is the link for same
https://www.freetds.org/userguide/ChoosingTdsProtocol.html
It does work, and apologies that the documentation is out of date. Microsoft is very good about maintaining backwards compatibility. I would recommend using TDS Version 7.4, if possible:
https://www.freetds.org/userguide/ChoosingTdsProtocol.html
Good luck!
Related
I'm new to MSSQL Hibernate, Previously worked with MySQL implementation
of Spring and hibernate.
I see the below supported list :
org.hibernate.dialect.SQLServerDialect
org.hibernate.dialect.SQLServer2005Dialect
org.hibernate.dialect.SQLServer2008Dialect
org.hibernate.dialect.SQLServer2012Dialect
I can't find support for the latest version of 2017 MSSQL server. It's okay to work with org.hibernate.dialect.SQLServer2012Dialect ?. Right now it works but i'm not sure how well it goes at a longer run.
Please suggest!
Thanks
Log.d
Yes, it is okay to work with org.hibernate.dialect.SQLServer2012Dialect for SQL Server 2017. As far as I know, SQL Server 2012 Dialect is the latest support NHibernate has for SQLServer.
Source: https://github.com/nhibernate/nhibernate-core/tree/master/src/NHibernate/Dialect
I receive the following error when running an R command for SQL in Visual Studio:
You are running version 9.0.1 of Microsoft R client on your computer, which is incompatible with the Microsoft R server version 8.0.3. Download and install a compatible version.
This page - https://msdn.microsoft.com/en-us/library/mt590540.aspx indicates:
To fix this issue, you can use sqlbindr.exe in the R Server 9.0 release to upgrade your SQL Server instance to the compatible 9.0 version. A servicing fix for SQL RTM CU3+ and SP1+ versions will be released in the near future.
I managed to find sqlbindr.exe by downloading the latest version of R server from Microsoft. Running this utility on my SQL Server does not seem to do anything. There may be some arguments needed.
I have SQL Server 2016 SP1 installed. I am able to execute the "Hello World" type example through TSQL.
Any ideas?
Edit: Through some trial and error I found that on the server running SQLBindR.exe with /list will show the instances of SQL presumably bound to R. SQLBindR.exe /bind seems like what I would need. But I get the message. "The instance must have a compatible version of SQL R Services (in-DB) installed. See for more details. "
So it seems like my SQL R Services is perhaps not updated correctly. I thought this would install via SQL Server SP1 and prior to that the installer.
Fixed (ish)
There seems to be some incompatibility between R Client 9.01 and SQL Server R Services although the compatibility chart indicates otherwise.
I found this very helpful post (http://www.desertislesql.com/wordpress1/?p=1340) that set me down the right path to figuring out the issue. Testing with a local context got rid of the error. I downloaded an older version of R Client from this Visual Studio Dev Essentials and that one worked.
I feel like based on the documentation the latest R Client should work, but I am not sure if there is a problem with my particular setup or the compatibility. Not sure yet what other issues there are with the old version of R Client, but at least it works now.
I think you need to install GDR update package for SQL Server 2016 SP1 which contains FIX: Version of R Client is incompatible with the Microsoft R server version 8.0.3. This was released without much fanfare on 12/16/2016.
I haven't tried this myself but I ran across a reference to the SQL 2016 SP1 GDR update today when reading other R Services MSDN docs.
I found a Microsoft document on SQL Server 2008 Express giving the hardware limits but am unable to find one on the 2016 version. Is it still 1GB?
I think that it should be 1GB.
This is a screenshot from Microsoft official site: https://www.microsoft.com/en-us/cloud-platform/sql-server-editions:
Hope it will help you.
I would like to set up SonarQube with Microsoft SQL Server (MSSQL). As of 05/27/2015, the requirements clearly state that SonarQube is supported with MSSQL 2008 and MSSQL 2012.
Has anyone tried setting up SonarQube with MSSQL 2014? If so, can you please let me know how it worked or did not work for you? If you are of knowledge of SonarQube's architecture, can you let me know if there are any architecture constraints that will prevent this from working?
I've been using it with MSSQL 2014 as described in the Ranger's guidance on SonarQube Installation guide. It's been working fine.
Regards - Jean-Marc
I'm trying to do a SQL Server 2008 setup and I've been given a Cross Language Installation failure. More specifically:
Rule "cross language installation: failed.
the Setup language is different than the language of existing SQL Server features. To continue, use SQL Server Setup installation media of the same language as the installed SQL Server features.
I do not have SQL Server Express installed and I browsed through "Add or Remove Programs" and was unable to find anything that looked like it was a previous version of SQL.
Any tips?
I restarted the setup after facing the same problem, and I realized that man should not close the installation center till the setup process is completed. If you leave it open it will work.
Ensure that you have uninstalled all of your old SQL Server versions. Also you must restart the installer if you have not done that when you began installation.
All I had to do was exit the installer and start the process again. For some reason it worked the second time around.
I had the same problem today when installing SQL Server 2008 Express on a computer that has never had an instance of SQL Server installed.
I found that "Microsoft SQL Server 2005 Backward compatibility" was installed. I removed this via Add/Remove Programs and was able to successfully install SQL Server 2008 Express afterwards.
Change the Current Windows Language interface for the needed language you want to install.
That will make it possible for the Installer to launch the Localized version.
If you've previously installed SQL on the machine (or apparently some RedGate tools) have you checked for any SQL detritus in the registry?
If not then the MS forums have details of some reg keys to look out for, and some of the links are worth following for advice on what to delete from the registry.
On my installation of Sql Server 2008 Express, this was caused by having Sql Server 2005 Express Tools installed while trying to install 2008. Uninstalling 2005 Tools fixed the problem. I was able to keep Sql Server 2005 Express, including Sql Server 2005 Backward compatability; only had to nuke tools.