Those commands will also drop all of the data pages from cache, forcing SQL to go to disk next time it needs data.

Do not run those on a busy production...

Traceflag 1222 is preferred over 1204 on SQL 2005 as it provides a lot more info. 3605 is not required for logging deadlock info to the error log.

To get deadlock...

Not possible.

The only database-scoped triggers are the DDL triggers that fire on schema changes. DML triggers have to be placed on each table and will fire when that table is...

ntext has a limit of 2GB. If the string is getting trimmed at 4000 characters, then it has something to do with how you're putting the data in or how...

Can you post one of the CREATE LOGIN statements that the script generated?

shekihan (11/26/2008)

---

By putting small table first you do assure that if the Query Optimizer (not a Query Analyzer of course) for some reason fails and decides to go your way...

No. It will enable page locks for the index specified in the alter index statement

what...

ALTER INDEX < Index name > ON < Table Name >

SET (

ALLOW_PAGE_LOCKS = ON

)

GO

Also you may want to revise that script. Both showconting...

Please don't cross post. It just wastes people's time and fragments replies.

Besides, I've already answered your post over here: http://www.sqlservercentral.com/Forums/Topic609456-147-1.aspx

No more replies to this thread please.

v.reddy (11/26/2008)

---

Are you sure Trace will show satements before execution?

You're welcome to check books online. All of the events are there along with their descriptions.

i belive trace will show...

No. Just try not to have multiple constraints/unique indexes on the column(s) referenced by the key.

You need to concatenate the variables into the string (beware SQL injection). They way your dynamic SQL is currently written, SQL's looking for two table variables, called @TableInput and @TableOutput...

I'm not a fan of dynamic SQL either, but it's the only practical way to get this working with more than around 3 parameters. With 3 or less, you can...

All of the foreign keys that the query return reference the Names table. Try dropping them.

It's odd, they should be referencing the pk, not the unique index.

I'm sorry if the support here isn't up to your expectations.

As I said in...