6

This was initially a bit of a mystery until I checked the IP of the azure SQL server. Googling for “azure sql cannot create PoolableConnectionFactory” I came across “Failed to Create PoolableConnectionFactory When Connecting to Azure SQL Server Database from Spring / Hibernate Tomcat Application” on MSDN with a recommendation to use user=username@...


4

For CD side it is easier, all DB related info is located in cd_storage_conf and deployer-conf files. After update just restart microservices. For CM side it is a little trickier since DB related info is encrypted using Tridion Rsa key. CM DB info is located in %TRIDION_HOME%\config\Tridion.ContentManager.config Topology Manager DB info is located in %...


3

You install the databases the same way you would do with a "regular" SQL Server, only this time the server address is of the Azure SQL, for example: & '.\Install Content Manager database.ps1' -DatabaseServer someAddress.database.windows.net -DatabaseName ... As far as Tridion (CME) is concerned it will work the exact same way. The same goes for all the ...


2

Besides Stefan's answer which covers all the scenarios, if you need to replace just the CM database, you can do it using the SDL Console (MMC snapin) so you don't have to tamper with config files.


Only top voted, non community-wiki answers of a minimum length are eligible