I want to migrate DataStage projects 11.3 to 11.7, I was wondering what problems there may be at the time of migration.
If you are using all the latest Stages/Connector in V11.3, you shouldn't hit any issues and it should be a simple export/import.
However, if you use some deprecated stages then you need to run the Connector Migration Tool to replace them - https://www.ibm.com/support/knowledgecenter/en/SSZJPZ_11.7.0/com.ibm.swg.im.iis.conn.migtool.doc/topics/connectormigrationtool_intro.html
You also need to check whether all the Source and Target you are using are still supported, e.g. Oracle Connector for V11.3 support Oracle 10gR2, 11gR1 and 11gR2 while V11.7 only support minimum of 11gR2.
Related
Currently we are using microstrategy as a reporting tool 11.1 version and using Oracle DB - micro strategy metadata, Statistics , history all installed in Oracle
now we are planning to move Db from Oracle to Postgres. just wanted to check if microstrategy support Potgres DB
Here is the list of certified and supported versions: Repositories
From personal experience I can say PostgreSQL v9,v10 and v11 runs fine as metadata repository. Tested v9-v12 as DWH too, all working without problems.
As far as I remember they didn't deliver the bundled driver in one of the MSTR-versions (2019-something), but that seems to have changed in MSTR-2020 again. Not a showstopper, but something to be aware of.
I am also running PG-11 as repo for History List too, but you definitely won't get help from support for this. OT: They even made me switch from MariaDB to MySQL for a support case (don't really blame them though, it's not certified and that's that).
My last attempt at running Statistics-Repo with PG is a long while ago and it didn't really work out of the box. Don't know what the situation is there. You might have to consider moving to PlatformAnalytics and/or MySQL(/MariaDB) for this too. EM only receives bugfixes from MSTR-2020 onwards, so this seems to be future-proof (EM discontinued from 2020 onwards?)
This mostly reflects our experience, the only certified PG version for MSTR 11.1 is PG-9 and only for the MD-Repo!
I have two TeamCity Servers which are running on different software versions: one server is running "TeamCity Enterprise 9.1.7" whereas the other Server is running "TeamCity Professional 7.0.2". What is the best way to perform a migration. I want to transfer the projects that exist on Server 7.0.2 to the Server 9.1.7.
I would be very grateful if you could provide me with the steps to undertake.
There are a lot of TC versions between 7.0.2 and 9.1.7, more than 4 years of updates: https://confluence.jetbrains.com/display/TW/Previous+Releases+Downloads
First of all, you should make a backup using maintainDB tool, then you can try to migrate from major to major version and test the results:
UPDATE: base on vlad-p53's comment you can migrate directly form 7.0.2 to 9.1.7, so, just follow the tutorial A Step by Step Guide to Migrating a TeamCity Instance from One Server to Another.
7.0.2 to 8.0 and test the results.
8.0 to 9.0 and test the results
9.0 to 9.1.7
If a migration to a major version does not work, you can try a previous versions and repeat the process.
Each release has a release note that explains if there is a migration issue, I recommend to you to read them.
To each migration you can follow the steps of this tutorial: A Step by Step Guide to Migrating a TeamCity Instance from One Server to Another.
I was going through upgrade process of mysql server. It is mentioned that to upgrade from 4.1 to 5.5 we need to upgrade step by step like first to 5.0,5.1 ...5.4 and then 5.5.
I have some questions :
What if we directly upgrade from 4.1 to 5.5. What might get effected? functionality or problem related to upgrading
Chances to loose data ? Even though I'll take backup using 'mysqldump --all-data-base' option.
Lets say, I have two database. I'll take only two database backup. I'll install latest version of mysql 5.7 and load two database back. What are chances to loose data or get corrupted ?
I'm curious to know this. If anybody tried? Because I need to do upgrade in live server.
Is there any step by step document which tells exact steps to upgrade from 4.1 to 5.5 in linux server
Major new features added to MySQL 5.0 and 5.1 that may not work/won't work in 4.x can be located here:
MySQL 5.0 - http://dev.mysql.com/doc/refman/5.0/en/mysql-nutshell.html
MySQL 5.1 - http://dev.mysql.com/doc/refman/5.1/en/mysql-nutshell.html
Is there a list anywhere or best practice instructions for update firebird databases from one version to another (in my case 2.1.3 to 2.5.2)?
I have seen backup and restore mentioned. I have updated from 1.5 to 2.1 in the past but that just worked i.e. I just installed the new firebird version, however I aware that this was probably just luck.
Regards
The Firebird 2.5.2 release notes has a section on compatibility issues that you need to be aware of when upgrading. Also the Firebird install directory contains additional info on upgrading in misc/upgrade/metadata/metadata_charset.txt. If your database has the incorrect metadata charset things might break (but AFAIK they would have been broken under Firebird 2.1 as well).
Technically you can upgrade to 2.5 without a backup and restore cycle on your database, but that means the On Disk Structure (ODS) of the database isn't upgraded to ODS 11.2, which could mean that you can't actually use some of the new features (or: performance improvements) introduced with the newer version. This could be worse if you are actually still on ODS 10.1 from Firebird 1.5.
I want to use Embedded FireBird with .NET 3.5. I have few queries:
(1) Are there any new developments done on the embedded version by the FireBird community?
(2) Are there any database file repair & optimize (shrink etc.) features in it?
(3) Does it supports Triggers, Foreign Keys, PL/SQL type of things etc.?
(1) Are there any new developments
done on the embedded version by the
FireBird community?
Yes, both the embedded and the client-server version are very active projects.
Using the same embedded version dll for ADO.NET for example, you can use the most recent version of the firebird engine dlls, even if the ADO.NET Firebird provider is not build for that version, but for a previous.
Check the issue tracker here: http://tracker.firebirdsql.org/secure/Dashboard.jspa
(2) Are there any database file repair
& optimize (shrink etc.) features in
it?
Yes, as described here: http://www.firebirdfaq.org/faq324/. You need to install the client-server version of firebird to use GFIX and GBAK from the command line. It is just a few megabytes.
Firebird does not have a "Compacting" feauture to shrink the database. You need to backup and then restore the database to do this. However you can use a firebird database for years without backup/restore (if you are lucky and the hard disk does not die). The only thing that you might need to do is to recalculate all indeces selectivity as described here: http://www.firebirdsql.org/dotnetfirebird/blog/2005/03/improving-query-performance-through.html
(3) Does it supports Triggers, Foreign
Keys, PL/SQL type of things etc.?
Yes. The 2.5 version of the embedded engine also supports accessing the same database file from different proccess at the same time.
Answering your questions:
The Embedded version is like a normal Firebird but encapsulated in a DLL and with some minor limitations. The Firebird Team just released some days ago the 2.5 version of SuperServer, Classic and Embedded flavors. More info at Embedded Firebird Server and Firebird website.
There are tools to repair and optimize databases. Check How to repair a corrupt Firebird database
Firebird is SQL:2003 conformant as stated in Firebird: SQL Conformance. It has triggers, foreiggn keys and stored procedures.
Hope that helps