Can't you simply open another connection to the database and fire the procedure asynchronously? That way it won't be part of the main application's execution path.

It's also worth pointing out that the ANSI 92 joins will cause problems in SQL Server 2005 and above when doing outer joins. From BOL: The outer join operators (*=...

dfalso (5/9/2008)

---

I don't think you're quite understanding my point (and I apologize if I'm not making myself clear enough). I'm not saying that I don't know how to use set-based...

Jane Matheson (5/9/2008)

---

I've thought about writing and even saved information I was working on for topics that I thought would be interesting. Why haven't I actually submitted an article?...

22?

Oh lordy, I knew you were wet behind the ears, but I had no idea. I could be your father... Oh, yuck. No offense, just lamenting my lost youth.

Anyway,...

Huh, I wonder why that's running slow. 😀

Sorry, that's not nice. Actually, except for the enormous set of columns in the GROUP BY, this isn't too bad a query based...

Rollback the transaction before you insert into your audit table. Here's a sample using Adventureworks:

BEGIN TRY

BEGIN TRANSACTION

UPDATE [HumanResources].[Department]

SET [Name] = NULL

WHERE [Name] IS NOT NULL

END TRY

BEGIN CATCH

ROLLBACK TRANSACTION

INSERT INTO dbo.[AuditLog]...

Just a quick follow-up. It looks like, based on the code you posted, that you're missing the concept of part of the UPDATE statement. You went inline on both your...

Great article Yoda: "you'll never wrong go by creating a primary key on a table, temp or not"

Seriously though, I find the resistance to your thoughts that, with a VERY...

Hey Sandy,

Are you getting lazy in your old age? 😉

Just go over to the MS web site and you'll get all the marketing stuff you need. Here's the page to...

You should look into breaking down your process into smaller steps. Insteading of processing one million rows (or whatever it is) as a single transaction, run them hundred thousand row...

I've always loved love writing. I hated English class in school because I thought, and still do, the teachers were, let's say, less than adequate to their jobs and more...

@@ERROR is resolved individually for each statement. So a bit of your code:

CREATE TABLE test1(testint int, oooo)

GO

IF @@ERROR<>0 OR @@TRANCOUNT=0

BEGIN

As long as the GO...

Take a look at INFORMATION_SCHEMA.PARAMETERS. It's a system view in your database.

Ah, I see where the problem might be:

(SELECT DISTINCT con.[ConsultantID]

...