AETLE site license usage question

The original question was about using sql server express for repository

An AETLE with centralized repository database(e.g. MSSQL Express) setup in a server

Although it is possible to use PosgresSQL or MySQL as repository it is rather too complex to set up so we always recommend using  MSSQL Express.

Found the repository connection for MySQL or PostgreSQL is only allowed for ODBC connection setting.
Any reason for only this option because we may choose these databases for repository?

This how it was originally created

Knew that there are different ways to add ODBC DNS to PCs but if this connection setting is controlled in centralized repository database for the mentioned cases.
Can the non ODBC DNS setting such as the existing  connection parameters setting for MySQL in ETL designer be allowed so that any updates of it can be automatically reflected to all PCs and it is not necessary to do the ODBC DNS step?

As long as the users connected to the same repository it will work.

EG

Two people are looking through the window; First one sees the bird; what the second person has to do to see the bird? 
 Two computers connected the same repository; First one creates new connection; what the second person has to do to see the connection? Refresh the object tree.

Hi Peter,


Just want to clarify if the AETLE of each PC needs to connect to the repository server( in my case MSSQL express), basically the related ODBC DSN should be manually added to each PC via ODBC manager and the related correct ODBC driver is installed or a bulky way via PowerShell.    


Best regards,

Kenny

MSSQL Drivers are usually installed part of operating system so there is no need to install the drivers

Our software works directly with PostgreSQL and MySQL so there is no need to install ODBC drivers.
(Importing data,exporting data running sql scripts )   

Hi Mike,

Thanks for your information.

Let me clarify my query again.

According to Peter's information
"Copy configuration from C:\ProgramData\ETL-Tools.com to rest of the computers"
So I think the copying of the configuration file from the source AETLE to other PCs can streamline the setup prcess. 
Then, I find the related connection setting records of the repository database in the connections.txt
And located MYETL=ODBC Connection,ETL,,,,-1 (i.e. my connection setting record in the connections.txt)
Since I used ODBC connection type for MSSQL, a DSN is required then I think a ODBC DSN should also be added to each PC. 


As per your further information, the connection string setup way of the oledb conection type for MSSQL can serve my purpose. And this way can be applied to Mysql and Postgresql repository database approaches.     

Thanks Mike again.

Kenny

 



 

Hi Kenny

Does it mean that we have answered all questions?  

Hi Mike,

The questions for case 1 and 2 are answered.

While new questions as below:

Looked the licensing server webpages and knew the setting mechanisms(i.e. input license information, add PCs information in licensing server, then register the license in the AETLE on each PC from the licensing server) 

In order to made the deployment easily, how can these steps be configured in the licensing server so that I do not need to do the register on each PC after the configuration file has been copied(i.e. the step 5 of case1)?

Looked the management console webpage and knew that the PCs information should be added to the repository database for monitoring.

Can the management console share the licensed PCs information in licensing server's repostory database so that I do not need to add PCs information again? 

Best regards,

Kenny