79614276

Date: 2025-05-09 14:00:12
Score: 3
Natty:
Report link

I had a similar error (130 unknown data type) but it was because the original field was created as a char instead of varchar. When I dropped and re-created the field as varchar, the migration to SQL Server worked.

Reasons:
  • Low length (0.5):
  • No code block (0.5):
  • Unregistered user (0.5):
  • Single line (0.5):
  • Low reputation (1):
Posted by: Phil Dunne