SQL Server 2014 support

0 vote

avatar

Hi,
I'm currently evaluating Remote Desktop Manager and Password Vault Manager and I'm very pleased with the complete solution. We're a software company in Sweden that has a suite of financial services software for the European market.


To the point, when purchasing Remote Desktop Manager Server we will put the database on a SQL Server cluster, preferably with SQL Server 2014. Do Devolutions support a SQL data source on a SQL Server AlwaysOn cluster today and when do you plan to support this with SQL Server 2014?


Thanks!


Regards,
Andreas Erson
Head of IT @
Aptic AB - Skövde, Sweden

All Comments (11)

avatar

I'm glad to here you like the software.

We have yet to test on SQL Server 2014 but I don't foresee any issues.

As for SQL Server AlwaysOn cluster. We do not have an environment available for testing hence I can't guarantee it will work but I feel pretty confident that it will work.

From what I understand after reading this article (http://msdn.microsoft.com/en-us/library/hh213417.aspx) is that you simply use the "Availability Group Listeners Name" like any other server name in the connection string. This means that AlwaysOn cluster is transparent to the application and it should work normally.

If you need any assistance in the configuring of the RDM Datasource please let me know.

Best regards,

Stéfane Lavergne

avatar

Hi,
How does your Admin-Feature (adding SQL-Users,..) work together with AlwaysOn?

To get a high availability we need the contained Database security.
http://blog.discountasp.net/partially-contained-databases-in-sql-server-2012/

This feature enables creation of userse that are used inside the database (not in the instance). This is needed for always on failover since there only the DB is mirrored.

Update:
I found out it creates the user at instance level (not god for always on).
edited by Peter Cermak (POI) on 1/23/2015

avatar

Push

avatar

Pushing again - Could you please consider implenting contained Database Login?

avatar

Peter,

I've added it to the to-do list.

Best regards,

Stéfane Lavergne

avatar

Looking forward and waiting impatiently ... ;-)

avatar

Peter,

In the next beta build will you have contained database "support". So the application should work on a DB that has CONTAINMENT = PARTIAL.

You will need to contain the database yourself (there is not option in RDM to do it automatically) Either create a new DB or modify a test DB.

You can have a look at converting an existing DB to contained: https://msdn.microsoft.com/en-us/library/ff929139.aspx

Example:CREATE DATABASE RDMContianed CONTAINMENT = PARTIAL
GO

ALTER DATABASE RDM SET CONTAINMENT = PARTIAL
GOPlease let me know if it works for you. In a future version we will add the UI elements to be able to create contained DBs directly in RDM.

Please do not test it on a production DB :-)

Best regards,

Stéfane Lavergne

avatar

Thank you very much Stefane!

I already have a Test-DB set up :-) I did a Backup/restore on my Always-On Cluster and edited the DB Settings manually via SQL Management Studio.

Do you have any idea or best practices how i can bring my existing Users from the "SQL Server Instance User Config" (Security - Logins) into the "Contained DB User Config" (Databaes - DB - Security - Users)?

Looking very much forward!! :-)
Best regards,
Peter

avatar

Take a look at the "Migrating Users to Contained Database Users" section of https://msdn.microsoft.com/en-us/library/ff929139.aspx It gave me an error trying to convert dbo so I filtered it out.

With the contained DB I was able a create a few users and login using those new users. I didn't dig much deeper than that. (aka I didn't test with a migrated user)

Best regards,

P.S. next beta build should be in a day or so.

Stéfane Lavergne

avatar

Hi,
I migrated the users with SQL cmds and they show up in the DB as users.
Unfortunately it ONLY does work when the user is ALSO allowed on the INSTANCE. RDM 10.9.0.0 64 bit
If the user is only in the Contained DB i get the attached errors.

I can connect via HeidiSQL - So this looks like you miss the DB-Definitin in the connection String of the Datasource Setup.
edited by Peter Cermak (POI) on 5/26/2015
edited by Peter Cermak (POI) on 5/26/2015

Capture_2015-05-26_10-38-06.png

Capture_2015-05-26_10-36-05.png

Capture_2015-05-26_10-34-29.png

avatar

Hi,
Could I please have an update on this issue?