Initial setup

[davidgray]

Hello, 

Just bought ASG remote desktop today.  I would like all our staff to share a central SQL server repository for their connections.  I have done the initial setup
however cannot get the environment to connect.   Each connection method I try gives the same error:



I have uploaded a couple of images to OneDrive and made them public, hopefully they can be viewed in this post.  

The message in the first one just says a "Connection could not be established", the second shows how my environment is setup. 

I have the database on a SQL 2014 developer edition
My domain account is as sysadmin 
Integrated throws the same connection error. 
I also tried with a SQL authenticated account but, after a very long pause, it also errors. 

Thanks in advance.

[DevOma]

Please upload an image how you configured your environment - just click the button "..." in login screen, select your environment and select Edit

Did you setup the environment by creating a new SQL database or perhaps do you refer just an empty database?!? In the next version the check of the selected database will be optimized with a more detailed error...

[davidgray]

Please upload an image how you configured your environment - just click the button "..." in login screen, select your environment and select Edit

Did you setup the environment by creating a new SQL database or perhaps do you refer just an empty database?!? In the next version the check of the selected database will be optimized with a more detailed error...

Hello, 
New database.  I initially tried an Azure SQL database and when that did not work I assumed it was because of it being a PaaS 
so I tried again with a SQL 2014 on a VM, same issue.   In noth cases I have full admin rights to the new database and indeed the 
test connection succeeded. 

I have attached a screenshot of how the environment is configured for the SQL database on VM. 

Thanks

[DevOma]

New database - but I want to know did you create the database within ASGRD - in environment setup you can choose to "Create a new database" - then a new database is created and all schema definitions and stored procs are created to access the database - or did you choose to "Connect to an existing database" and choose an empty database on your SQL instance? That won't work…

If you have Administrator rights on the database server you should be able to access the database you just have created before. Did you create the database from the same machine using the same account?

And AZURE SQL Database should also work - if you create the database by the wizard after choosing "Create new database using AZURE SQL"

[davidgray]

New database - but I want to know did you create the database within ASGRD - in environment setup you can choose to "Create a new database" - then a new database is created and all schema definitions and stored procs are created to access the database - or did you choose to "Connect to an existing database" and choose an empty database on your SQL instance? That won't work…

If you have Administrator rights on the database server you should be able to access the database you just have created before. Did you create the database from the same machine using the same account?

And AZURE SQL Database should also work - if you create the database by the wizard after choosing "Create new database using AZURE SQL"

Hello, 
I created the databases (PaaS and IaaS) first, added the relevant security then tried to connect. 

I will try re-creating the PaaS from scratch.  We tend to create PaaS database with their own backend server at the same time, however if I use ASG 
I will have to put the database on an existing backend server.  I'm not 100% sure "backend" is the correct terminology for what I mean so I have attached 
a screenshot

[DevOma]

Yes but you can't connect to an empty database - you have to create the schema by using ASGRD database wizard - else the "Connection test" will be successful because you can connect the database - but you can't work with that database because has no valid content - this check will be implemented in the next version too :-)

[davidgray]

Yes but you can't connect to an empty database - you have to create the schema by using ASGRD database wizard - else the "Connection test" will be successful because you can connect the database - but you can't work with that database because has no valid content - this check will be implemented in the next version too :-)

Ok so I picked a server that I have dbmanager (sysadmin in old money) and attempted, via the wizard to create a new database on this Azure SQL Server (PaaS) 
I cannot get past the info message because it says the database does not exist.  I know it does not exist as I selected "create new database" in the previous step. 

Two attachments show these steps. 

Thanks

[DevOma]

Ok - might be a bug in current version - can you try the same on your local SQL server?

[davidgray]

Ok - might be a bug in current version - can you try the same on your local SQL server?

Hello, 
Yes it works with a SQL 2014 instance on a VM.  The setup for PaaS does not appear to be correct though or I'm missing something. 

Screen 1
Select - Create a new database (AZURE SQL)

Screen 2 
Enter SQL db url, database name & credentials 

but... The option to create a new db is greyed out. 

I've attached screeenshots to shows these two steps. 

So, is it not possible to use PaaS ? 

Thanks

[DevOma]

Currently I have no AZURE environment available - so it would take some time to get it working / testing again.

I think there was a problem trying to create the database on AZURE - so you need to do this step manually - just create a database on your AZURE environment and try to execute again

Else you can migrate every local database to AZURE - there is a wizard from MS SQL Tools that guide you through this process - I know some other customers did that in the past...