How to hide triggers from SQL Server?

Hi,
I wonder whether there is a way to temporarily hide triggers from SQL Server
2000, SQL Server 2005 and SQL Server 2005 Express. The reason that I want t
o
do this is because even though I disable triggers, SQL Server will take time
s
to evaluate whether the trigger is disabled or not. Based on my own testing
,
an alter table statement can be 2 to 3 times faster without trigger comparin
g
to disabled triggers.
Thanks for any help,
PeterHi Peter
Disabling the triggers is the best you can do unless you drop and re-create
them.
Out of interest Is there alot of code in these triggers or are they nested?
John
"Peter" wrote:

> Hi,
> I wonder whether there is a way to temporarily hide triggers from SQL Serv
er
> 2000, SQL Server 2005 and SQL Server 2005 Express. The reason that I want
to
> do this is because even though I disable triggers, SQL Server will take ti
mes
> to evaluate whether the trigger is disabled or not. Based on my own testi
ng,
> an alter table statement can be 2 to 3 times faster without trigger compar
ing
> to disabled triggers.
>
> Thanks for any help,
> Peter|||Hi Peter
Disabling the triggers is the best you can do unless you drop and re-create
them.
Out of interest Is there alot of code in these triggers or are they nested?
John
"Peter" wrote:

> Hi,
> I wonder whether there is a way to temporarily hide triggers from SQL Serv
er
> 2000, SQL Server 2005 and SQL Server 2005 Express. The reason that I want
to
> do this is because even though I disable triggers, SQL Server will take ti
mes
> to evaluate whether the trigger is disabled or not. Based on my own testi
ng,
> an alter table statement can be 2 to 3 times faster without trigger compar
ing
> to disabled triggers.
>
> Thanks for any help,
> Peter

How to hide triggers from SQL Server?

Hi,
I wonder whether there is a way to temporarily hide triggers from SQL Server
2000, SQL Server 2005 and SQL Server 2005 Express. The reason that I want to
do this is because even though I disable triggers, SQL Server will take times
to evaluate whether the trigger is disabled or not. Based on my own testing,
an alter table statement can be 2 to 3 times faster without trigger comparing
to disabled triggers.
Thanks for any help,
PeterHi Peter
Disabling the triggers is the best you can do unless you drop and re-create
them.
Out of interest Is there alot of code in these triggers or are they nested?
John
"Peter" wrote:
> Hi,
> I wonder whether there is a way to temporarily hide triggers from SQL Server
> 2000, SQL Server 2005 and SQL Server 2005 Express. The reason that I want to
> do this is because even though I disable triggers, SQL Server will take times
> to evaluate whether the trigger is disabled or not. Based on my own testing,
> an alter table statement can be 2 to 3 times faster without trigger comparing
> to disabled triggers.
>
> Thanks for any help,
> Peter