Or do a search in the little box near the top of the page. You'll find tons of discussions and articles and scripts on the topic, all on this site.

As far as I know, you're going to have to monitor that table. That means setting up some type of service to check the table periodically and respond to the...

Do you mean something like this:

ALTER TABLE dbo.X

ADD CONSTRAINT MyConstraint

FOREIGN KEY (aa,bb)

REFERENCES dbo.Y(aa,bb)

Like that?

BOL should give you most of what you need.

I strongly recommend using the TSQL commands to run the profiler job, not the gui. I also recommend placing the output...

I didn't see it, so I'd add the TextData column as well. Other than that, you've covered the basics.

You don't need the Profiler gui. Actually, better still if you don't have it. There are several ways you can get the scripts, including generating them locally through your own...

Gather statistics on both sides of the equation. Guessing or pointing at various bad signs won't help. You need a reasonably thorough picture of what is occurring. For example, do...

Two options, write a function that takes the comma delimited list and turns into a table or pass the list in as XML and use OPENQUERY or XQuery to join...

It's most likely the server, but I'd gather some information to back yourself up. Use profiler to get a days worth of data, hopefully including a timeout or two. Go...

Have you run Profiler to identify the poor performing processes? If not, I'd do that right away. You say it's a third party vendor. Once you've identified badly behaved procedures,...

Gail gave it to you

SET NOEXEC ON

Put that in front of the query with a semi-colon seperating it from your code. This works against Adventureworks:

SET NOEXEC ON;

SELECT * FROM...

Just a quick clarification, 2008 isn't supposed to ship until Q2 2008. Personally, I wish they'd wait until Q4, 2009.

If you want to parse it from your client, use the code that Gail provided from there.

First try running DBCC CHECKDB(). From the sounds of things, that'll probably fix it. If not, you've got work to do. Can you restore it from backup? If not, you...

And wrap it all in a transaction.

Also, make sure you include the old data values in the update statement. That way, if the second call manages to get the same...