By default there's a button that looks like a scroll with a disk in front of it that is "Generate Change Script." Clicking on that button will show the script...

It's a database mail error.

There isn't a single answer to a question like this. I'd start by looking over the best practices as listed by Microsoft here: http://www.microsoft.com/technet/prodtechnol/sql/bestpractice/default.mspx

Specifically some information on storage:

That sounds odd. That's a database mail error. According to BOL either the profile specified doesn't exist or the user running doesn't have permission to access the profile. You may...

Ah, those wonderful 3rd party apps.

I really found next to nothing documented on that process. You may want to open a call with MS. I'd also contact the vendor and...

SP2 seems to introduce almost as many problems as it fixes. That said, if I were doing an install today and didn't face one of the specific issues that SP2...

Since this posted in SQL Server 2005, why not use nvarchar(max)? No problems there, stores the same data.

What about using sp_msforeachdb along the lines of

'SELECT [TABLE_NAME]

FROM ?.INFORMATION_SCHEMA.TABLES'

Substitute where you need to. This works across all the database and eliminates the need for a cursor.

I've mainly grown my best practices over time. We record them locally as we discover new ones that we didn't know we need. MS has some help in this area....

It must be a system proc. There's not only nothing BOL. There's nothing at MSDN. There's nothing at TechNet. There's precious little on a google search. What are you mucking...

Sure, it's a common table expression. It's new in 2005. They function similar to derived tables, but can be referenced multiple times in a give procedure and, most importantly for...

And the recursive section of BOL has an example doing almost exactly what is being requested here. You ought to be able to take the example & make it...

We took a script from SQL Server Central that checked fragmentation and then decided whether or not to reindex or defragment (great script, used it for years, I'm not sure...

Oops. Did a bit more testing & found you need to add this at the end:

OPTION(MAXRECURSION 0);

Or you could...

No promises on performance but:

DECLARE

@BeginDt DATETIME;

DECLARE @EndDt DATETIME;

SET

@BeginDt =