Hi,
has anybody here experience with updating a MDS client (CU update) on a seperate server without a SQL Server engine?
If I use a regular SQL server update setup package it will not update anything because the SQL Server engine is missing...
I am afraid to update the backend SQL Server to this CU... MDS might not work anymore after that.
Or... is the only thing I need the update database option in de MDS client itself?
I am not a MDS user or admin, just the database administrator who is responsible for lifecycle management.
It seems Microsoft gives me a hard time updating this client.
The reason it is on a seperate box is that I don't want to have the IIS role on a SQLServer instance server. Instaling the MDS client without an engine is no problem at all. MDS itself works good.
Is that not also best practice?
Can someone give me any hints on this...?