Very Computer

by **Henrik Larsso** » Sat, 14 Sep 2002 14:53:46

Hi,

I'm having quite a strange problem with my SQL Server installation.

Somehow values in a field becomes negative, which they should never be. The
same operation seems to apply to all records in the database, but I'm not
certain of that. The application consists of both asp.net pages and a c++
program, and I don't know in which part the error is or where it could be.

Is there any way of tracking this error on the database level? For instance
setting up some watchdog or trigger that reports the last SQL statement sent
when the values becomes negative? or some other way to find the error?

It's running SQL Server 2000 Enterprise edition with SP2.

Thanks,
Henrik

by **Andrés Taylo** » Sat, 14 Sep 2002 15:10:19

Hej Henrik,

If the columns are never supposed to have a negative value, I'd suggest a
CHECK for it. This will prevent the error from occuring again. Other than

information from sysprocesses, when negative values appear.

HTH,

--

Andrs Taylor

http://www.sql.nu/

> Hi,

> I'm having quite a strange problem with my SQL Server installation.

> Somehow values in a field becomes negative, which they should never be.
The
> same operation seems to apply to all records in the database, but I'm not
> certain of that. The application consists of both asp.net pages and a c++
> program, and I don't know in which part the error is or where it could be.

> Is there any way of tracking this error on the database level? For
instance
> setting up some watchdog or trigger that reports the last SQL statement
sent
> when the values becomes negative? or some other way to find the error?

> It's running SQL Server 2000 Enterprise edition with SP2.

> Thanks,
> Henrik

by **Tibor Karasz** » Sat, 14 Sep 2002 15:28:31

I guess one could even combine an instead of trigger and a check constraint. That allow for
"catching the criminal" and making sure that data isn't corrupted. But one would have to write
the triggers, and write them correctly, of course :-)

--
Tibor Karaszi, SQL Server MVP
Archive at: http://groups.google.com/groups?oi=djq&as_ugroup=microsoft.public.sql...

> Hej Henrik,

> If the columns are never supposed to have a negative value, I'd suggest a
> CHECK for it. This will prevent the error from occuring again. Other than

> information from sysprocesses, when negative values appear.

> HTH,

> --

> Andrs Taylor

> http://www.sql.nu/

> > Hi,

> > I'm having quite a strange problem with my SQL Server installation.

> > Somehow values in a field becomes negative, which they should never be.
> The
> > same operation seems to apply to all records in the database, but I'm not
> > certain of that. The application consists of both asp.net pages and a c++
> > program, and I don't know in which part the error is or where it could be.

> > Is there any way of tracking this error on the database level? For
> instance
> > setting up some watchdog or trigger that reports the last SQL statement
> sent
> > when the values becomes negative? or some other way to find the error?

> > It's running SQL Server 2000 Enterprise edition with SP2.

> > Thanks,
> > Henrik

by **Henrik Larsso** » Sat, 14 Sep 2002 19:26:51

I've never used either triggers or check constraints, could anyone help me
with the syntax or procedure to create them for this problem?

Thanks
Henrik

Quote:> I guess one could even combine an instead of trigger and a check

constraint. That allow for

Quote:> "catching the criminal" and making sure that data isn't corrupted. But one
would have to write
> the triggers, and write them correctly, of course :-)

> --
> Tibor Karaszi, SQL Server MVP
> Archive at:

http://groups.google.com/groups?oi=djq&as_ugroup=microsoft.public.sql...

> > Hej Henrik,

> > If the columns are never supposed to have a negative value, I'd suggest
a
> > CHECK for it. This will prevent the error from occuring again. Other
than

more
> > information from sysprocesses, when negative values appear.

> > HTH,

> > --

> > Andrs Taylor

> > http://www.sql.nu/

> > > Hi,

> > > I'm having quite a strange problem with my SQL Server installation.

> > > Somehow values in a field becomes negative, which they should never
be.
> > The
> > > same operation seems to apply to all records in the database, but I'm
not
> > > certain of that. The application consists of both asp.net pages and a
c++
> > > program, and I don't know in which part the error is or where it could
be.

> > > Is there any way of tracking this error on the database level? For
> > instance
> > > setting up some watchdog or trigger that reports the last SQL
statement
> > sent
> > > when the values becomes negative? or some other way to find the error?

> > > It's running SQL Server 2000 Enterprise edition with SP2.

> > > Thanks,
> > > Henrik

Very Computer

error-tracking

error-tracking

error-tracking

error-tracking

error-tracking