Page 1 of 2

Timeline for SQL Server 2016 support

Posted: Wed 23 Sep 2015 15:06
by gw123
I noticed Red-Gate added 2016 support. When will SQL Complete have this?

Thanks!

Re: Timeline for SQL Server 2016 support

Posted: Wed 23 Sep 2015 15:27
by alexa
Unfortunately, we do not make support for CTPs. SQL Server 2016 will be supported in dbForge after it is officially released.

Re: Timeline for SQL Server 2016 support

Posted: Mon 21 Mar 2016 18:42
by gw123
2016 is in RC1 and I believe feature complete. Every other major SQL add-in already has 2016 support. Please implement this support soon!

Re: Timeline for SQL Server 2016 support

Posted: Mon 28 Mar 2016 10:23
by alexa
Could you please let us know whether you are referring to supporting SSMS 2016 or the new features of SQL Server 2016?

Re: Timeline for SQL Server 2016 support

Posted: Mon 25 Apr 2016 08:50
by jbond312
Is there any update on this? I am trying to use SQLComplete and now require the use of SQL2016 and I am unable to use this product.

Re: Timeline for SQL Server 2016 support

Posted: Mon 25 Apr 2016 11:29
by alexa
Syntax highlighting when working with SQL Server 2016 will be supported in the next version of dbForge SQL Complete. Integration of dbForge SQL Complete into SSMS 2016 will be possible after SQL Server 2016 RTM is officially released.

Re: Timeline for SQL Server 2016 support

Posted: Wed 27 Apr 2016 15:20
by Andrew Buis
I am also looking for SSMS 2016 integration. Any chance for a beta release for CTP3? Missing SQL Complete is the last piece I need for switching to 2016 SSMS as my daily driver.

Re: Timeline for SQL Server 2016 support

Posted: Thu 28 Apr 2016 12:23
by alexa
At the moment, we are working on supporting the new functionality of SQL Server 2016. We do not make support for CTPs. SSMS 2016 will be supported in dbForge SQL Complete as soon as the final release of SSMS 2016 is available.

Re: Timeline for SQL Server 2016 support

Posted: Fri 03 Jun 2016 14:31
by asharovarov
SQL Server 2016 was released. Do you have a date for SQL Complete Release with support of the new version?

Re: Timeline for SQL Server 2016 support

Posted: Fri 03 Jun 2016 15:12
by alexa
We are currently working on this and are planning to release the new build of dbForge SQL Complete with support for SQL Server 2016 as well as SSMS 2016 this month.

Re: Timeline for SQL Server 2016 support

Posted: Wed 08 Jun 2016 13:47
by DanyVDS
Thanks for the info

Re: Timeline for SQL Server 2016 support

Posted: Thu 07 Jul 2016 01:18
by avi.bookwala
This was due to be released last month. Could we please get an update as to when the new version is set to be released?

Re: Timeline for SQL Server 2016 support

Posted: Fri 08 Jul 2016 08:53
by alexa
It's moved forward for about 1 week. We will notify you as soon as it's available for downloading.

Sorry for the inconvenience.

Re: Timeline for SQL Server 2016 support

Posted: Thu 21 Jul 2016 09:41
by .jp
Hello,

We are very pleased to announce the new version of dbForge SQL Complete v5.5 with support for SQL Server 2016 and SQL Server Management Studio 2016.
If you already use the tool, just "Check for Updates” in dbForge SQL Complete to upgrade to the new version.

Here is a new features list www.devart.com/news/2016/dbforge-sql-complete-v55.html .

Feel free to email us if you have questions connected with the new version of our add-in, we'd like to help.

Best Regards.
Devart Team.

Re: Timeline for SQL Server 2016 support

Posted: Thu 21 Jul 2016 18:32
by fkhan
I just installed SMSS 2016 and then tried to install SQL Complete v5.5.136 Express and it does not recognize that SSMS 2016 is installed on my computer. The option is grayed out. What is the problem?

UPDATE: I got it working by creating a registry entry for SMSS 2016 in the right place as follows:

The setup program was looking for en entry at: SOFTWARE\WOW6432Node\Microsoft\AppEnv\10.0\Apps\ssms_13.0

However SMSS 2016 during its installation created its entry at
SOFTWARE\WOW6432Node\Microsoft\AppEnv\14.0\Apps\ssms_13.0

By duplicating the 14.0 key at 10.0, the setup program detected the correct location and went forward with the installation.