Access ODBC does not recognize automatic client reroute
Hi, I have an ODBC connection to a DB2/LUW database in MS/Access (2016) and am trying to implement ACR (Automatic Client Reroute). I have added the following (bold) to my db2dsdriver.cfg file: <database name="MYDBASE" host="DBHOST1" port="60000"> <parameter name="hostname" value="DBHOST1"/> <parameter name="port" value="60000"/> <parameter name="AltHostName" value="DBHOST2"/> <parameter name="AltPort" value="60000"/> <acr> <parameter name="enableAcr" value="true"/> <parameter name="maxAcrRetries" value="10"/> <parameter name="acrRetryInterval" value"1"/> <parameter name="enableseamlessACR" value="true"/> <parameter name="enableAlternateServerListFirstConnect" value="true"/> <alternateserverlist> <server name="otherserver" hostname="DBHOST2" port="60000"/> </alternateserverlist> </acr> </database> I have tested this on my machine and it successfully falls over to the alternate server when the primary server is unavailable. However, when I attempt to connect to the database in MS/Access, I get a connectivity error (SQL30081N) Has anyone worked with MS/Access and ACR? Thanks!Transform Machine Learning Research into a Professional Product with Azure
Throughout my time at university, I have built any number of scikit-learn, Tensorflow, or PyTorch machine learning models. However, if we start building with Azure from the very beginning, Azure’s MLOps offering provides an end-to-end solution for the ML life-cycle, from training and building the model initially, to continually retraining / redeploying an up-to-date service. Azure MLOps can even help us compare model performances & automatically detect data drift
ACR purge based on number of containers
I have a need to define a number of containers to keep rather than purging based on age. I found https://docs.microsoft.com/en-us/azure/container-registry/container-registry-auto-purge about creating a task but it only seems to support removal by age. Searching further I found a https://github.com/goyalmohit/acr-cleanup which would do the job but I was wondering what the best way to implement this might be. I don't want to spin up a VM just for this job to execute so I considered a container scheduled to start, run the script, and then stop. But is there anyway I can create some sort of scheduled task within Azure itself to run this?
