Last post Apr 04, 2014 07:06 PM by aabruzzese
Apr 04, 2014 02:25 PM|nvielbig|LINK
I'm currently sifting through a solution trying to find where we have an insert into the table of interest that is allowing them to insert a null value for a column that shouldn't be allowing nulls. The column is nullable (this table has existed long before
I worked here), so it's allowing nulls to go in if the query says to. I need to find where in this entire solution this insert is taking place, but that's very difficult because it could be all over the place, and I don't know exactly what the end
users are doing to cause this.
Is there a way to setup a trigger of some sort that says "if a record is inserted here with column 'x' null", create a record in table y with x,y,z, information. Essentially, I don't really see myself identifying the root
of this error in the application, there are too many scenarios that this table is inserted/updated and it's not as simple as looking at objects all over the place to track their values -- lots of hard-coded queries exist in the code-behinds.
Is there a way to setup a trigger of some sort that says "if a record is inserted here with column 'x' null", create a record in table y with x,y,z, information.
I appreciate any help you may be able to provide me with, any clarification needed please dont hesitate to ask.
Apr 04, 2014 07:06 PM|aabruzzese|LINK
do you have a development copy?
If so, change the column attribute and then try running the solution again and see if you get lucky, others I would start profiler on the the SQL server to see
what queries are running, or perhaps someone here might have the answer as well.