Thanks so much for this script - it's fantastic!

The only issue I ran into is that some of our job names and step names have single quotes in them, which...

To do this, you have to create a clustered index on the table and specify the new file group for the index - once you've moved it, you can drop...

I've fixed the redirection on my blog, so you can view it now. I must have changed the layout at some point and not set up this forwarding page properly.

Sorry...

Thanks for re-formatting the query - I'll see if I can get that fixed on the posted version of the script.

As far as Stored procs, it looks like you can...

I've updated this script to do a few additional things, like

- Properly re-create unique indexes

- Handle Included columns

- Do "online" index moves w/error handling - creates new index, drops old,...

You could take care of the NULL by using an ISNULL, and replacing a NULL value with the date from the first column. As far as the multiple consecutive rows...

Actually, after giving it some thought, it could be done using a subquery. It would take a long time, as it would have to look up through the table for...

I think the point is to display one value while it's effective, and then display the new value once the data changes. In this case, rows one and two would...

I figured out my own problem. The first thing was that I didn't get that transaction levels apply to the data reader, not the transaction owner, so it really didn't...

I've found a workaround for this, so I thought I'd post it here. It's described here:

http://blogs.conchango.com/jamiethomson/archive/2005/08/20/2048.aspx

Though it's not a real solution to the problem, it works fine for...

In doing some investigation on my own code, I've encountered some REALLY strange transaction behavior in SQL2K. When I ran just the "BEGIN TRANSACTION", followed by a "SELECT @@TRANCOUNT", I...

I checked more thouroghly through the code, and I don't get any errors at all, so I'm totally clueless as to why this is happening. Is there a chance that...

Is there a better way to handle this? I could do error handling after each statement - something like:

--------------------------------------------

IF @@error 0

GOTO LABEL_ROLLBACK

--------------------------------------------

I would have that statement after each TSQL...

In my procedure, if I remove the BEGIN TRANSACTION and COMMIT TRANSACTION, the script runs just fine and commits at the end. The reason that I do the conditional commit...

I looked for a little bit, also, and there don't seem to be any other workarounds available. Since you don't want to be bothered by the error message, and you...