Actually, you've got it right. It's going to update alll the rows from one table where the id's match in the second table.

Maybe you phrased the question wrong or I...

Once you identify the offending procedure using Gail's method, get execution plans to see what is occuring within the script.

Do you foresee a need to use character sets from other languages, Kanji, Cyrilic, what have you? No, use VARCHAR. Yes, use NVARCHAR.

99.999% TSQL.

The remaining bits I use C# or VB.NET through the SMO (SQL Management Object). Very little need for anything else.

I did go through a great book on using PERL...

montgomery johnson (12/3/2007)

---

Does anyone have a script that would help me identify users that are resource hogs? I need to know who is a resource when I run my script...

Gail is 100% correct. To add to it a bit, if your statement uses an index to retrieve the data, it frequently comes back in index order. The only way...

Or, I didn't think that through all the way and I'm wrong.

If you have a primary key constraint defined as nonclustered, you already have an index on that column, so no worries there.

Yes, you don't have to include the clustered index...

It simply gives you an indication whether the error is informational, really important, fatal to a connection or fatal to the server. See the reference linked above for details.

I went and read the original message. It's whining, pure and simple. I then read as many of the comments as I could stomach. It's kind of freaky how attached...

The real problem is, I am a jerk. So I have to try to reduce the damage as much as possible. Emails are dangerous because, even a well crafted message...

Sorry, I wasn't trying to upset anyone. I'm serious. I screw up all the time. The checks I can put in place to prevent my own errors will help those...

In order to select FROM something, it needs to be a table valued object (table, view, function, temp table, table variable, OPENXML, XQuery). You can run a query against a...

What about literally breaking the query up into smaller queries? You can call them all from a single wrapper query. You get more discrete, tuneable execution plans and you can...

Works like a charm too... until the first time a request...