Showing results for 
Search instead for 
Did you mean: 

NULL errors after SQL move

Level 4

migrated to a new sql server and everything came up and works but over the past few weeks i notice lots or errors in the ev event log that it can't insert null values. the fix seems to be going in to ssms and for the particular table modify the columns to allow nulls by ticking the checkboxes.

as anyone seen this or know why this happens, or how to get around it?


Level 6
Partner Accredited Certified

open up a case with symantec because just changing tables and columns is a really bad idea and could be indicative of bigger problems or cause way bigger problems in the future

Level 4

curious if anyone has ever seen this. more of an MS issue than veritas.not sure if it was something with the way the dbs were migrated or not. anyone?