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
Related
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!
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
version of my database is 661.
when i attach my database in new version of sqlserver, version of my database changed to 665
Automatically.
I don't want to change version of my database.
how can i do that?
You can't prevent automatically database version upgrade when you're attaching/restoring database from lower to higher version of SQL Server.
Source: A lot of years of experience.
BUT, you can do a manual migration of higher version database into lower version by doing THIS
Well, I think you are using SQL Server 2008 R2 database which are 661 version. Hopefully you are trying to attach 2008 R2 to an SQL server 2008 instance but once the database has been upgraded to an 2008(665 version), it cannot be downgraded to SQL Server 2008 R2(661).
You need to uninstall SQL Express and reinstall the latest version to fix the problem.
You can't stop it changing the version, when an older version database is attached to a newer version of SQL server, it must perform these upgrade steps so before the database can be brought online on the new version. These upgrades are internal to SQL server and include things like file format changes etc, they themselves should not affect behaviour of your user code (although the changes in the new version of the SQL engine might).
The only significant result of these upgrade steps is that the database can no longer be attached or restored to an older version of SQL server.
i am new to hibernate and need to configure it for MS SQL-server 2012 standard.
i found this deprecated article how to configure hibernate config file for sql server but i need a new one. where i can find the driver for the new database (if there is any)!
thanks for answers
I was able to get it working with Microsoft JDBC Driver 4.0 for SQL Server as seen here.
jTDS didn't work although it had previously worked with the same settings on SQL Server 2008 R2.
A couple config lines which MS JDBC 4.0 requires.
jdbc.driverClassName=com.microsoft.sqlserver.jdbc.SQLServerDriver
jdbc.url=jdbc:sqlserver://localhost:1433;
No need to give the user,password and database name in separate property tags,you can keep all of them inside url named proprety tag.
Inside Hibernate configuration file you can write like this:-
<property name="connection.url">jdbc:sqlserver://myhost;user=user1;password=pass1;database=Student1</property>
where user1,pass1,myhost and Student1 are my credential, you can replace them by yours.
to close the question: i am using oracle now. not because ms is not working...
the upper config could work...
I have a previously developed project that I am working on now. The project uses SubSonic 2.1 as ORM and it has been working fine since we decided to move to a newer server. The new server has SQL Server 2008 SP1 and now SubSonic is not behaving as usual.
I debugged the case and found that SubSonic is now generating ANSISQL queries instead of SQL Server friendly ones. I found a solution with 2.2 (customizing IsSqlServer2008 method) but I can't migrate to SubSonic 2.2 because project is really big and has lots of lots of SubSonic queries.
How can I make SubSonic 2.1 to work with SQL Server 2008 SP1?
Thanks
Tell it that you using SQL Server 2005?
2005/2008 are close enough in the sense that 7.0/2000 were.
Edit: What I mean is, override whatever so SubSonic thinks you're on SQL Server 2005.
I've never used SubSonic but your question implies you can override IsSQLServer2008 so is there a IsSQLServer2005 for older versions?
Thanks for replying. I decompiled the old dll and customized the IsSql2008 method and Sql2008Generator class. Now it works like a charm.
other problem is in sql 2000, because SQL2000 notification has in version number string "2008" , subsonic try tu use 2008 query (for paging) in 2000, and of course there is big mess.
So for SQL2000, last good subsonic 2.x version is subsonic 2.1.