Here comes one of those "awful" questions you didn't want to get.... Are you SURE a value is being passed through for the parameter (when you're firing this from...

Unless fillable means "I have a blank spot after I print that I can write on", then - no.

Reports are not data-entry mechanisms. What you're looking for would be...

You might be returning NULL values in your WHERE clause which can make comparisons fail flat out.

luckysql.kinda (7/22/2009)

---

No don't use instead of trigger.

I would like you to go ahead and enable default trace on by using sp_configure command. now you can easily see all the logs...

create something that uses it as a foreign key. It should error the delete out.

The Database Tunig advisor... one of the features in SSMS you can use to figure out what might be missing.

It tends to be overeager on some index recommendations. ...

...and if the tablock isn't enough, limit your deletes to a certain number (which you can determine on execution), and just keep fire the delete off serveral times until the...

..+ hunter +.. (7/21/2009)

---

Yup this code is in the trigger. I know this scripts is more efficient but i need to loop it to avoid the transaction context is in...

(this very question was already asked a couple of times on here.)

It's a resource issue. Check the other answer I've already posted for more specifics.

http://www.sqlservercentral.com/Forums/Topic756846-386-1.aspx

Ankur Bajaj (7/21/2009)

---

Disabling access is not an option as there might be 100s of users,anyone of whom might run the backup command.

Heres the solution I have tested and which is...

...disable the access?.....

As far as I know - you can't hand a DDL trigger off of a BACKUP command.

From the reference on the DDL triggers:

Trigger on a CREATE, ALTER, DROP,...

That is the specific error. Looks like three warnings came up:

Login Timeout Error

An error has occurred while establishing a connection to the server. When connecting to SQL Server 2005,...

what are you using to determine what is "returned" from the update?

Take a look here:

http://blogs.msdn.com/sqlclr/archive/2006/03/24/560154.aspx

Essentially - CLR uses memory external to SQL, so you may need to increase the "memtoleave" so that CLR has some room to work.

(if you turn off the "create" and "drop" options, you will ONLY get the permissions).