Forums

[mingleforum]

Comments (2)

  • Idana

    |

    Your article perfectly shows what I needed to know, tankhs!

    Reply

  • namanthakral

    |

    got errors after executing this trigger
    “SQL SERVER – Fix : Error : 17892 Logon failed for login due to trigger execution. Changed database context to ‘master’.”

    and was really stucked in this mess but DAC saved my life
    C:\Users\Administrator>sqlcmd -S LocalHost -d master -A
    1> DROP TRIGGER block_ipaddress ON ALL SERVER
    2> go

    Reply

Leave a comment

CAPTCHA Image
*

Recent Comments

VidhyaSagar

|

Thanks Ashish, I’ve updated the script.

Ashish

|

I was just searching some trace related articles and gone through your article. Found one incorrect information,
to disable the trace, the command should be
dbcc traceoff (….)
you might have by mistake mentioned it as traceon for disabling as well.

Ben

|

I remember having to write a complicated procedure to do the same thing recently. This will be nice to use with a web app to only return a small subset. I think this will improve the speed especially when the entire result set is very large.

namanthakral

|

got errors after executing this trigger
“SQL SERVER – Fix : Error : 17892 Logon failed for login due to trigger execution. Changed database context to ‘master’.”

and was really stucked in this mess but DAC saved my life
C:\Users\Administrator>sqlcmd -S LocalHost -d master -A
1> DROP TRIGGER block_ipaddress ON ALL SERVER
2> go

Rating