on 2024 Mar 26 1:17 PM
Hi,
We are upgrading from DM stack 11 to Stack 21.
The plan is to setup a new server PROD-NEW due to upgraded support software (windows SQL etc.) and perform export import function from PROD-OLD to prod new.
Will there be a problem importing to the new environment?
Is there something specific that needs to be done as part of the export/import in this case?
Regards,
Eyal
Request clarification before answering.
Hello Eyal,
There really isn't too much of an issue. As of Stack 1000, you can go from any version to the latest one, without having to install any intermediary versions.
My suggestion
- on your new DM application sever
- install Stack 2100, and point to the existing DB. This will upgrade the DB to 2100 level
- install Task Engine and DM client (and mapper)
If you want, you can then move the DB to a new server (simply at SQL level, with backup/restore)
Marc
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hello Eyal,
From 1100 to 2100.... ?
I doubt that will work - there have been so many changes since. Transport should normally be done with source and target systems on the same version
May I ask - why this 'export/import" - if you upgrade the existing system to 2100, there is no need for all this importing of periods
Marc
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Marc,
Thank you.
The idea is to avoid upgrading each of the MS components. Also there might not be enough time between quarterly reporting to upgrade and test the server. Therefore a Prod-new. We plan to setup up a new server with the updated environment (windows, SQL Office). “Prod-New”.
After that install DM stack 11 and then import and then upgrade DM to stack 21.
There may be a problem with this approach - correctly installing DM stack 11 with Windows server & SQL Server versions that are only supported from much more recent DM Stacks. But then, it’s only to upgrade DM right away to stack 21.
Option #2 – is to copy the server as is with existing Windows versions SQL DM, then upgrade each component – Windows/ SQL .NET and then DM we have a similar situation - Upgraded components and DM Stack 11 before upgrade though already installed.
A third option is to copy the server as is, like #2, and first upgrade DM to stack 21 and only after update the Microsoft components.
What do you suggest?
Regards, Eyal
User | Count |
---|---|
10 | |
10 | |
2 | |
2 | |
2 | |
1 | |
1 | |
1 | |
1 | |
1 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.