Hi Magarity,

Absolutely the way to go once the process is stable and populated on an incremental basis.

Tell me, I gather from the discussions on the subject that there is only...

Hi Centexbi,

This sounds really interesting - I will give it a try as soon as I can.

Thanks for the idea!

Adam

Hi There Casinc835,

Thanks for the input!

After 60 -odd days and a 10% increase in volumes (and admittedly a lot of design changes) we are not seeing any notable increases in...

Hi Magnus,

Of course, you are absolutely right that your approach is faster, but, as you point out, it reauires complete control of the entire process. Also (which I did not...

Hi Joel,

Thanks for this idea - but can you confirm that processing large data sets in batches like this is faster overall for the entire dataset? My (admittedly hazy) memory...

Thanks to all for the comments, and for isolating the points needing clarification.

Certainly, this is not the only way to do things, and it is only a suggestion, wich probably...

Nice article Boyan, - I found it extermely interesting.

Here is the code for pr_RunAgentJob:

Sorry about the non-inclusion

CREATE PROCEDURE [dbo].[pr_RunAgentJob]

(

@JobName VARCHAR(200)

)

AS

/*

This procedure is a wrapper for the sp_start_job stored procedure.

It tests whether the job is running before allowing the...

Hilarious this one, thanks for the link.

Now, when you consider that I wrote this a couple of months ago, I really should concentrate on guessing the lottery numbers...:-)

Hi David et al,

I am the one who owes apologies, I have no idea how the tagging corrupted the article presentation, and I am sorry that this happened.

I will attempt...

Hi Spencer,

Thanks for the tips on maintenance plans, I had not encountered this and it is well worth knowing.

Adam

OOPs- My apologies to all who hit permissions problems, you need to add something like:

"CodeGroup class="UnionCodeGroup"

version="1"

PermissionSetName="FullTrust"

Name="MyCodeGroup"

Description="Code group for...

Hi Steve & Sinh,

You could need to look at:

adding a code group to the rssrvpolicy.config - http://support.microsoft.com/kb/842419 (explains this particular error)

or:

http://msdn.microsoft.com/en-us/library/ms154466(SQL.90).aspx

- for an overview of custom assembly security.

Let us all...

Hi Sinh,

I have no idea off the top of my head about this one. I will have to spend some time looking at the deeper security implications of this process...

Oops! Sorry about the typo - the ";" in the first snippet before CASE should, of course, be a comma!