question

emanuelegemelli-2907 avatar image
0 Votes"
emanuelegemelli-2907 asked Cathyji-msft commented

Micorosft SQL Server migration assistant errors

Hi everybody,
I'm trying to migrate a DB2 database to SQL Server using Microsoft SQL Server Migration assistant.
After I run the report, I see some errors without any suggestion to fix them.

Have you already used this tool?
I have already read Microsoft webpage without any help.
Do you have any suggestions?



sql-server-migration
· 1
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

Hi @emanuelegemelli-2907,

Any update for this thread? Did the replies could help you? If the response helped, do "Accept Answer". If it is not, please let us know. By doing so, it will benefit all community members who are having this similar issue.  Your contribution is highly appreciated.

0 Votes 0 ·
Cathyji-msft avatar image
0 Votes"
Cathyji-msft answered

Hi @emanuelegemelli-2907,

After I run the report, I see some errors without any suggestion to fix them.

The Assessment Report window shows the results of the conversion of database objects to Transact-SQL syntax. The Error List pane shows error, warning, and informational messages.

What the error message that you got? Could you share them to us for analysis?

5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

emanuelegemelli-2907 avatar image
0 Votes"
emanuelegemelli-2907 answered AlexanderIvanov-MSFT commented

DB22SS0083 identifier Mx06 cannot ne converted because it was not resolved

The main problem is an Add constraint not null.. do you know how I can convert it?
Thanks

· 1
5 |1600 characters needed characters left characters exceeded

Up to 10 attachments (including images) can be used with a maximum of 3.0 MiB each and 30.0 MiB total.

Hello,

SQL Server supports NOT NULL constraints - simply mark your column as NOT NULL or issue an ALTER table ALTER COLUMN column <type> NOT NULL. There is probably more to it than you have shared with us, as standard "not null" constraints should be automatically converted. Can you share:

  1. What version of SSMA you are using

  2. DB2 version

  3. Original SQL definition of the table that is causing issues

  4. SQL text that SSMA produced

Feel free to reach out to us using Help -> Feedback option within the tool.

Regards,
Alex.




0 Votes 0 ·