Forum Discussion

MaxBronder's avatar
MaxBronder
Frequent Visitor
2 years ago
Solved

Can not insert null value error for nulllable column

During an INSERT statement I´m always receiving this error  The column here is defined as nulllable and I even recreated the table multiple times to assure that. The error also appears if I´m...
data warehouse
  • MaxBronder's avatar
    MaxBronder
    2 years ago

    Hi Anonymous 

    Thanks for your answer, unfortunately the column was neither primary key, foreign key or use in calculations.

    Nethertheless I found a solution, or more like a workaround.

    The columns in the Insert statement have been in a different order than the columns were ordered in the create table. So indeed, there were NULL values for a not null column, but it was not the one displayed in the error message, but the one that would have been in the same position in the table.

    So for me that sounds like a bug.

    Thx and KR Max

  • Anonymous's avatar
    Anonymous
    2 years ago

    Hi MaxBronder ,
    I have checked with the internal team. There is no active bug for such a scenario currently. 
    But you could share your feedback on our feedback link which would be open for the user community to upvote & comment on. This allows our product teams to effectively prioritize your request against our existing feature backlog and gives insight into the potential impact of implementing the suggested feature.
    Feedback Link : Home (microsoft.com)
    Thank you.

MaxBronder's avatar
MaxBronder
Frequent Visitor
2 years ago

Hi Anonymous 

Thanks for your answer, unfortunately the column was neither primary key, foreign key or use in calculations.

Nethertheless I found a solution, or more like a workaround.

The columns in the Insert statement have been in a different order than the columns were ordered in the create table. So indeed, there were NULL values for a not null column, but it was not the one displayed in the error message, but the one that would have been in the same position in the table.

So for me that sounds like a bug.

Thx and KR Max

Anonymous's avatar
Anonymous
Not applicable
2 years ago

Hi MaxBronder ,
Thanks for the inputs. In the above comment , are you trying to say that the error message displayed in SSMS was different from the actual error?

  • MaxBronder's avatar
    MaxBronder
    Frequent Visitor
    2 years ago

    Anonymous yes exactly, the wrong column was mentioned in the error.

    • Anonymous's avatar
      Anonymous
      Not applicable
      2 years ago

      Hi MaxBronder ,
      Thanks for the information. Glad that your issue got resolved.
      I will check with the internal team regarding the error in SSMS.
      Appreciate your patience.

      • Anonymous's avatar
        Anonymous
        Not applicable
        2 years ago

        Hi MaxBronder ,
        I have checked with the internal team. There is no active bug for such a scenario currently. 
        But you could share your feedback on our feedback link which would be open for the user community to upvote & comment on. This allows our product teams to effectively prioritize your request against our existing feature backlog and gives insight into the potential impact of implementing the suggested feature.
        Feedback Link : Home (microsoft.com)
        Thank you.