--- In vantage@yahoogroups.com, Jose Gomez <jose@...> wrote:
>
> I am seeing this all over my error logs. We are SQL 8x any ideas?
>
> You tried to compare or to update a character field with a value longer
> than the maximum length.
>
> *Jose C Gomez*
> *Software Engineer*
> *
> *
> *
> *T: 904.469.1524 mobile
> E: jose@...
> http://www.josecgomez.com
> <http://www.linkedin.com/in/josecgomez> <http://www.facebook.com/josegomez>
> <http://www.google.com/profiles/jose.gomez> <http://www.twitter.com/joc85>
> <http://www.josecgomez.com/professional-resume/>
> <http://www.josecgomez.com/feed/>
> <http://www.usdoingstuff.com>
>
> *Quis custodiet ipsos custodes?*
>
>
> [Non-text portions of this message have been removed]
>
On Sat, Jun 22, 2013 at 6:35 AM, s1mhall <s1mhall@...> wrote:
> **
>
>
> Jose,
> It may be a few things. If everything has been going along ok error free
> then it could be that you have a corrupt index on the SQL box or even a
> table. Check the SQL error logs for anything unusual. If you don't have any
> maintenance plans in place to keep track of your SQL DB then this would be
> a good time to start. You can use the once created with the DB Maintanance
> Plan Wizard or you can grab some DB admin type scripts from places like
> DB_Forums. They are a good source of information about SQL.
>
> If you do need to do anything then a good place to start is doing a DBCC
> checkdb, BUT please make sure you read any details about running the
> command as you can break things. SQL books online is an excellent resource
> for this also.
>
> I hope I am not telling you to suck eggs here, but if you can, restoring a
> copy of the database and playing with that is always a safe option.
>
> If you do have all of these things in place and SQL is not reporting any
> errors then it may be something as simple as a problem in the DB creation
> scripts from Epicor and they have a field that is in progress side that has
> more characters than in the SQL DB. Typically if you were using SSMS with a
> query and you perform an update or a an insert into a predefined table
> (permanant of temporary) manually you would get a message stating "Sting or
> Binary Data will be truncated". It may be that the progress log error is
> being translated from SQL in that fashion to get the error that you are
> seeing.
>
> Finally I have never seen this happen in our environment so I can only go
> on what information and experience dealing with SQL for the time I have
> been using Epicor products.
>
> I hope that helps.
>
> Cheers
> Simon
>
>
> --- In vantage@yahoogroups.com, Jose Gomez <jose@...> wrote:
> >
> > I am seeing this all over my error logs. We are SQL 8x any ideas?
> >
> > You tried to compare or to update a character field with a value longer
> > than the maximum length.
> >
> > *Jose C Gomez*
> > *Software Engineer*
> > *
> > *
> > *
> > *T: 904.469.1524 mobile
> > E: jose@...
>
> > http://www.josecgomez.com
> > <http://www.linkedin.com/in/josecgomez> <
> http://www.facebook.com/josegomez>
> > <http://www.google.com/profiles/jose.gomez> <
> http://www.twitter.com/joc85>
> > <http://www.josecgomez.com/professional-resume/>
> > <http://www.josecgomez.com/feed/>
> > <http://www.usdoingstuff.com>
> >
> > *Quis custodiet ipsos custodes?*
> >
> >
> > [Non-text portions of this message have been removed]
> >
>
>
>
[Non-text portions of this message have been removed]