Cool but there is a problem: I've been using SSMA for DB2 for a month now and I can see that the feature Save as SSDT project has changed to Save as SSIS project.
I've exported the package and is impossible to load it on Visual Studio: after a few minutes it freeze. The root cause might be:
- SSMA is creating a package that has connection to DB2. But once you export that package to another machine without direct connection to the DB2 the package makes Visual Studio freeze
- The package in my case has 898 tables with all sort of datatype conversion, it weight 35Mb and therefore is too big to import and makes Visual Studio freeze? (I'm using a DELL latitude 5501)
In both cases the feature is unusable because:
- It's normal to export packages to local laptops in order to work on it
- It's normal for a DB2 database developed in the '80 - '90 to have 1000 tables
the SSMA tool overall is good but that specific feature is unusable.
Microsoft
