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
Related
I believed that I always got the latest version of SQL Server when creating a new Azure database from the Azure Portal. But that is not happening.
I always get sql Server version (12.0.2000.8) which is SQL 2014. I can't find other places to set a new compability level either.
Is there a problem with my subscription (pay as you go)??
Have any of you had the same experience as me, have you been able to solve it?
The reason I want SQL 2017 is that I want to publish SSIS packages to the SSISDB catalog, which is not possible on SQL 2014?
Hope any of you can help me out here
regards GEir
It's possible to use SSIS on DB engine 12 on Azure. Check out official documentation.
Additionally, you may upgrade your already-created azure databases by setting COMPATIBILITY_LEVEL modificator. Look into ALTER_TABLE documentation for examples.
Please note that although SQL Azure's engine share similar "engine api" as SQL Server 2014 (v12), those are not the same. What's more relevant in terms of supported features is maximum supported "Compatibility level".
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'm new in this field, please kindly help me.
I'm installing pentaho biserver for community in my notebook. At first, it's succeed (with default configuration) like this. but, when I'm trying to change the database with ms sql server like this tutorial,
help.pentaho.com/Documentation/5.4/0F0/0K0/040/0D0
an error occurs:
Can anybody tell me what's wrong with the installation?
I'm using:
Sql server developer edition 2014
pentaho biserver community 4.8.0
apache-tomcat-8.5.3
jdk8
sql server driver sqljdbc42.jar and I put it under \biserver-ce\tomcat\lib
I also try something like Using Pentaho Community Edition with SQL Server 2005 but still not working.
switch to default configuration. no need to do anything. while creating Datasource connection Pentaho provides option for connecting to different RDBMS database.You just need to place JDBC connector file into lib directory.
I'm having a tough time integrating moodle with sqlserver through FREEDTS even after reading the documentation in the moodle site.
I've setup the settings in freedts.conf,php.ini and Config.php.
But, inspite of all this it does not connect to my database. I'm using SQL Server 2008.
What could I possibly be missing?
Thanks.
Have you built PHP with support for FreeTDS as described in the FreeTDS User Guide?
I was able to get it running with SQL Server 2008 and IIS by following the guide from BFC Networks. The primary thing was using SQL Server 2.0 for PHP to complete the integration.
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.