Re: Item 2:

The idea is to move your ROOT tag out a level and add the username element before the rest of the stuff. I don't have your tables so...

Re: item 1

Is that your actual XML? If so I see two issues:

1. You have dashes prefixing some of your lines:

2. You have unescaped quotes in some attributes:

<name first_name=""?""...

Yikes :crazy: MS = Microsoft? Which version of CRM?

giles.clapham (3/25/2011)

---

The simpler suggestion you mention...

What will be consuming your results? Doing this kind of work else outside the DB is also a viable option. Most reporting tools have built-in functionality well-suited for solving running...

My bad...I misread the question. SAVE TRANSACTION will let you save the inner work you've done provided you issue a COMMIT after you issue a ROLLBACK to a named savepoint...but...

Access how? Read or Write? To which event log?

You can write errors to the Application Event Log using RAISERROR:

RAISERROR('Hello World!',16,1) WITH LOG ;

You can read or write to any Event...

Yes, you can use a cursor. This is one of my few universally acceptable uses of a cursor on SQL Server. You could also take a look at the undocumented...

SAVE TRANSACTION will do what you need:

http://msdn.microsoft.com/en-us/library/ms188378.aspx

I just noticed that your proc is not calling itself...I took that for granted initially based on previous posts.

That said...you're welcome for the quick demo on the recursion limit...

Lowell is referring the maximum recursion level, not the max transaction level. Since your proc calls itself you need to be aware of it. Try this out in your test...

I would like to help...can you provide the DDL for both tables attached as a .sql file and maybe some DML to create a few rows. This way I can...

OK...I'll take a shot at this...

I noticed something in your Audits table design that should be mentioned...UNIQUEIDENTIFIER might be the worst choice on the planet for the first column in...

Do you know about TRY/CATCH? You can report on trapped error, but it only sees the last error so you'll lose sight of the "DBNAME does not exist error".

BEGIN TRY

...

If you're going from SQL Server to SQL Server I would use the native option of bcp instead of character ( -c ). Not only will it be faster but...

Dang it Lutz...I was almost there! You got it!