Rule disappeared

I seem to have a rule on one of my columns which prevents me from entering a
value above 25000 in an integer column.
I am not able to find the rule so that I can delete it.
Is there a system table that I should look for?
This table was upsize from Access to SQL 7.0
Are you sure it's a rule you are looking for? If you used
the upsizing wizard, it should have implemented this as a
constraint.
What are you using to manage SQL Server and where are you
looking? You really don't want to address this by modifying
system tables.
To view information as well as constraints, rules on a
table, you could execute:
EXEC sp_help YourTable
To check for constraints, you can execute:
EXEC sp_helpconstraint YourTable
-Sue
On Wed, 19 Jan 2005 08:51:06 -0800, "Arne"
<Arne@.discussions.microsoft.com> wrote:

>I seem to have a rule on one of my columns which prevents me from entering a
>value above 25000 in an integer column.
>I am not able to find the rule so that I can delete it.
>Is there a system table that I should look for?
>This table was upsize from Access to SQL 7.0
|||Sue,
I executed the two command that you suggested. There seem to be another
hidden constraint that I can't find.
"Sue Hoegemeier" wrote:

> Are you sure it's a rule you are looking for? If you used
> the upsizing wizard, it should have implemented this as a
> constraint.
> What are you using to manage SQL Server and where are you
> looking? You really don't want to address this by modifying
> system tables.
> To view information as well as constraints, rules on a
> table, you could execute:
> EXEC sp_help YourTable
> To check for constraints, you can execute:
> EXEC sp_helpconstraint YourTable
> -Sue
> On Wed, 19 Jan 2005 08:51:06 -0800, "Arne"
> <Arne@.discussions.microsoft.com> wrote:
>
>
|||Constraints don't typically hide so...let's start over.
Could you please post what you are doing and what tool or
application you are using? And post the exact error message
you are receiving?
-Sue
On Thu, 20 Jan 2005 06:11:04 -0800, "Arne"
<Arne@.discussions.microsoft.com> wrote:
[vbcol=seagreen]
>Sue,
>I executed the two command that you suggested. There seem to be another
>hidden constraint that I can't find.
>"Sue Hoegemeier" wrote:
|||Sue,
I am inside enterprise manager. I try to change the quantity from 6000 to
26000 in an integer column. I get a message that says the current Maximum is
25,000.
We create a new column called quantityNew and with the same datatype and
content. QuantityNew can be changed with no problems.
Arne
"Sue Hoegemeier" wrote:

> Constraints don't typically hide so...let's start over.
> Could you please post what you are doing and what tool or
> application you are using? And post the exact error message
> you are receiving?
> -Sue
> On Thu, 20 Jan 2005 06:11:04 -0800, "Arne"
> <Arne@.discussions.microsoft.com> wrote:
>
>
|||The only way I can think of that you can get a message like
that is through a trigger. If it was a rule or a constraint,
you'd get a much more verbose message indicating that it
violated a check constraint or a rule, the column it was on,
the name of the constraint if it violated a check
constraint, etc.
Check for triggers on the table. In Enterprise Manager,
right click on the table, select All Tasks and then select
manage triggers.
-Sue
On Thu, 20 Jan 2005 10:45:03 -0800, "Arne"
<Arne@.discussions.microsoft.com> wrote:
[vbcol=seagreen]
>Sue,
>I am inside enterprise manager. I try to change the quantity from 6000 to
>26000 in an integer column. I get a message that says the current Maximum is
>25,000.
>We create a new column called quantityNew and with the same datatype and
>content. QuantityNew can be changed with no problems.
>Arne
>"Sue Hoegemeier" wrote:
|||Sue,
I finally found the offending trigger. Thanks.
Arne.
"Sue Hoegemeier" wrote:

> The only way I can think of that you can get a message like
> that is through a trigger. If it was a rule or a constraint,
> you'd get a much more verbose message indicating that it
> violated a check constraint or a rule, the column it was on,
> the name of the constraint if it violated a check
> constraint, etc.
> Check for triggers on the table. In Enterprise Manager,
> right click on the table, select All Tasks and then select
> manage triggers.
> -Sue
> On Thu, 20 Jan 2005 10:45:03 -0800, "Arne"
> <Arne@.discussions.microsoft.com> wrote:
>
>
|||Glad it's fixed! Thanks for posting back the results.
-Sue
On Thu, 20 Jan 2005 13:43:09 -0800, "Arne"
<Arne@.discussions.microsoft.com> wrote:
[vbcol=seagreen]
>Sue,
>I finally found the offending trigger. Thanks.
>Arne.
>"Sue Hoegemeier" wrote: