We have 3 instances, Production, Test and development.
At some point we need the same data from production in the test system (maybe in dev too).
Is there something that can be used to copy all data from production server to Test to be 100% sure that the data (and all cycles) are the same?
(plus copying enhancement configuration)
Not only one cycle, the whole data!
AFAIK, SAS does not provide tools for synching SAS datasets between environments so you pretty much have to build your own processes. Third party or OS tools are one option. SAS tools like SAS/CONNECT can be useful as you can copy a whole library using PROC UPLOAD
How is your data stored? Is it SAS datasets? Since they are files, then this would be a file copy task, and there are plenty of utilities for doing batch file copy /synching etc.
If your data are in databases, then you might use database tools to clone your PROD database to make a TEST database.
Not sure what you mean by "copying enhancement configuration").
If you can describe your environment more (e.g. SAS 9 server or Viya, where is the data stored...) people will be able to offer better advice.
On a SAS 9 BI server with metadata, there are some tools that you can use to automate extracting metadata so that can it can copied and loaded.
It's SAS 9, thought Via is only a cloud solution?
Data is stored in SAS Datasets and of course in the default PostgreSQL databases
Technical I can copy all around but what about:
Hostnames in PostgreSQL databases(!) we are not aware of, there are a few used by the solution.
Hostname in SAS configurations, wherever it is?
EnvironmentManager and and and
License that we keep TEST license ...
Ahh, sorry, I didn't realize that SAS Solution for IFRS17 is a separate product aka "solution":
https://www.sas.com/en_us/software/solution-for-ifrs-17.html
I still don't understand how these different "solutions" that SAS sells relate to SAS 9 (or Viya).
I won't be able to help with this. If you don't get other answers here, would try asking tech support.
I'm not sure if and how easily that would be possible. It's certainly something you want to discuss with SAS directly before even attempting to do so.
The SAS Risk projects I've been in didn't have test strategies that required full data replication. Using the same config files like libnames.txt and the same parameter and payload data in the landing area for the months that got tested was considered sufficient.
All config and parameter files and the like were version controlled via git which made it ease to ensure that the same versions existed on different environments.
The SAS Users Group for Administrators (SUGA) is open to all SAS administrators and architects who install, update, manage or maintain a SAS deployment.
SAS technical trainer Erin Winters shows you how to explore assets, create new data discovery agents, schedule data discovery agents, and much more.
Find more tutorials on the SAS Users YouTube channel.