...
[11:24:44 CDT(-0500)] <jwennmacher> vcrowley: did they have this error on 4.0.7 or is the situation it is just appearing now they are trying to migrate to 4.0.9.1?
[11:26:22 CDT(-0500)] <EricDalquist> so I'm not seeing anything obvious in that diff that would have changed column types
[11:26:26 CDT(-0500)] <EricDalquist> perhaps this was already there
[11:26:34 CDT(-0500)] <EricDalquist> one option for a "just reboot" style fix
[11:26:54 CDT(-0500)] <EricDalquist> would be to just drop and recreate the up_raw_events table
[11:26:57 CDT(-0500)] <EricDalquist> and see if that fixes it
[11:27:09 CDT(-0500)] <EricDalquist> or try doing an initportal on a new sqlserver db with 4.0.9.1
[11:27:13 CDT(-0500)] <EricDalquist> and see if they get the error tere
[11:27:32 CDT(-0500)] <EricDalquist> trying to see if this is a bug with 4.0.9.1 on sqlserver or with upgrading from an existing database schema
[11:29:39 CDT(-0500)] <jwennmacher> makes sense.
[11:33:54 CDT(-0500)] <vcrowley> i do not believe this was seen with 4.0.7
[12:18:29 CDT(-0500)] <jwennmacher> EricDalquist: On the sqlserver error, this was on a clean dev environment post initportal. They tried SQLServer2005Dialect, SQLServer2008Dialect, jTds driver (1.3.x), and Microsoft JDBC v4 driver. Same issue as I understand it.
[12:19:13 CDT(-0500)] <jwennmacher> You think there is there a reason to have them try 4.0.11 just to see?
[12:59:41 CDT(-0500)] <EricDalquist> yeah
[12:59:59 CDT(-0500)] <EricDalquist> I would be interested to see if 4.0.11 fixes it
[13:00:02 CDT(-0500)] <EricDalquist> otherwise it will be a bug
[13:00:08 CDT(-0500)] <EricDalquist> and we'll have to figure out how to fix it